debian 1.11.0-1 package looks broken without cffi, enum34, pycparser #2765
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2765
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I updated my debian/sid box to the new
tahoe-lafs-1.11.0-1
debian package today, and also did anapt-get autoremove
which removedpython-cffi
andpython-pycparser
.The resulting
/usr/bin/tahoe
fails at startup, because of our (#2749) internal version checks. The error message looks like this:In retrospect, that's not actually a failure, but the successful list of versions scrolled off the screen, and what was left visible looked like a failure, so I'm going to claim that this is still a problem (to be fair, I'll note that
tahoe create-introducer
ran without noise).We need to remove the transitive dependencies from our
_auto_deps.py
.To fix this on Debian, I think the Debian package needs to either patch
_auto_deps.py
(which might involve patching*init*.py
, I'm not sure), or re-introduceDepends:
on the packages it wants (python-cffi
,python-pycparser
, maybe? I don't even know what that enum34 thing is, it's not in ourinstall_requires=
but it is listed in_auto_deps.py
).Or just delete all of
*init*.py
like #2749 suggests :).Installing
python-cffi
(which pulls inpython-pycparser
) is not sufficient to make it stop complaining. It changes the warning message for those two packages, though:Debian has since updated their package. Debian is also dropping Tahoe-LAFS due to lack of Python 3 support.