updates to indirect dependencies cause build failures #2468
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#2468
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Consider the case where Tahoe initially depends on foo >= X.0, and foo X.0 depends on bar Y.0. Then foo X.1 is released which depends on bar Y.1. (This is a common situation, especially when foo and bar have overlapping development teams.)
Suppose that a particular machine has bar Y.0 installed globally. What is supposed to happen is that, in the case where a Tahoe build on that machine downloads foo X.1, it also downloads bar Y.1 and builds it under
support/
.However, that doesn't happen. Instead we get an error:
For a concrete example, see https://tahoe-lafs.org/buildbot-tahoe-lafs/builders/memcheck-32/builds/96/steps/compile/logs/stdio:
setuptools delenda est.
If mutable deployment environments are your thing,
pip install --upgrade
takes care of this now. I'd recommend not upgrading in-place, though. Wipe and re-install clean. Maybe this is awful but it's also awfully practical. And is Tahoe-LAFS really going to fix the Python package management and installation toolchain? Doubtful.