[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4133: fix tahoe packaging

[Tahoe-LAFS]

#4133: fix tahoe packaging
-------------------------+-----------------------
     Reporter:  meejah   |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  n/a
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------

Comment (by btlogy):

 So, lets recap the current situation after having merged
 [https://github.com/tahoe-lafs/tahoe-lafs/pull/1395 #1395]:

 == Nix on CircleCI Docker runner
 - the builders were failing after as the did before because of the Cachix
 issue described in ticket:4134
 - the builders previously fixed in [https://github.com/tahoe-lafs/tahoe-
 lafs/pull/1403 PR#1403] are now failing again because they still have to
 be adapted to the new hatch build system.
 - we know how to build the package with hatch, but we are still missing a
 way to pass `allmydata.test.test_client.Basic.test_versions`.

 => WiP in [https://github.com/LeastAuthority/tahoe-lafs/pull/12
 LAfork/PR#12] and [https://github.com/tahoe-lafs/tahoe-lafs/pull/1403
 PR#1403]

 == Other linux on CircleCI Docker runner
 - the builders that were left (based on `debian-11`, `ubuntu-20.04` and
 `ubuntu-22.4`) can setup the new resulting virtual-environment with hatch
 build and unit test the code just as they did before (with the well known
 flakiness described in ticket:4126).
 - however, those same builders would not be able to complete the `create-
 virtualenv.sh` w/o new system dependencies introduced by hatch (gpg module
 requires gpgme devel package): see ticket:4143 and [https://github.com
 /tahoe-lafs/tahoe-lafs/pull/1409 RP#1409] which should cover the new
 requirements.
 - we've also uncovered a possible problem with the newer images we were
 planning to built on (`debian-12` and `ubuntu-24.04`): `gpgme-config` is a
 tool required for `tahoe-lafs[build]` part which seems to have been
 removed from the `gpgme` package v1.18.0 provided in those new images:
 more details from this [https://github.com/tahoe-lafs/tahoe-
 lafs/pull/1409#issuecomment-2535375966 comment].

 => We may want to investigate and report this bug upstream (if confirmed).
 Or we might just remove the need for this new dependency on `gpgme` as it
 is only needed to sign wheels (which we do not do on CI today).

 Apparently, this has already been proposed by meejah in
 [https://github.com/tahoe-lafs/tahoe-
 lafs/pull/1410/commits/c8db39e1aa2809d712b6144f830068fff13633b7 c8db39e].
 Though I do not thing this commit belong to [https://github.com/tahoe-lafs
 /tahoe-lafs/pull/1410 PR#1410] which focuses on Python 3.8 being EOL
 (ticket:4131).

 == Other native runners on CircleCI and !GitHub
 - packaging, unit and integration tests + coverage: all those seem to do
 fine with hatch build system.

 => Nothing else to do there.

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