[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4143: Refresh docker builder images

[Tahoe-LAFS]

#4143: Refresh docker builder images
------------------------------------+-----------------------
     Reporter:  btlogy              |      Owner:  btlogy
         Type:  task                |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by btlogy):

 After a few tweaks:

 - version of docker can not longer be pinned in the CircleCI image
 (comment:4),
 - `gpgme` develop package to be added as a new system dependency,
 - postponing new `debian-12` and `ubuntu-24.04` images due to a possible
 breaking [https://github.com/tahoe-lafs/tahoe-
 lafs/pull/1409#issuecomment-2535375966 change] in newer `gpgme`.

 a first round of update has been successfully triggered by meejah earlier
 today from the tip of [https://github.com/tahoe-lafs/tahoe-lafs/pull/1409
 PR#1409], and the master has successfully built once using them.

 Next step is to alter some of builders to use the new/re-activated images.
 Optionally, I wonder if we should not pin the builders to the latest
 digests, so we can prepare and publish new images later w/o impacting the
 ongoing PRs (but then, when do we pin again? - probably need thinking with
 ticket:13).

 - `debian-11`, `a-local`, `another-local` and `ubuntu-22.04`: nothing to
 do (else than optionally pinning),
 - `ubuntu-20.04`: remove and replace by `ubuntu-24.04` (and optionally
 pinning)
 - `fedora-35`: remove and replace by `fedora-40` (and optionally pinning)

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4143#comment:5>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage