Unable to pip install tahoe-lafs directly without first installing PyOpenSSL #2570
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
4 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2570
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?
On a debian system I'm unable to successfully run
pip install allmydata-tahoe
due to a compilation error while installingpyOpenSSL
. However, if I first runpip install [PyOpen](wiki/PyOpen)SSL
and thenpip install allmydata-tahoe
then this succeeds.Notice how in the first case the package which fails to install is called
pyOpenSSL
but in the second sequence of commands, the package requested isPyOpenSSL
with an initial capitalP
. Is this the difference? Can we change the dependencies of tahoe-lafs to refer to the successfully installing pacakage?Here's the first attempt to install
allmydata-tahoe
:If I install
PyOpenSSL
(with a capitalP
) directly first, then I can installallmydata-tahoe
, as seen here:I believe the capitalization of pPyOpenSSL is a red herring. Package names should be case-insensitive.
This issue seems to no longer persist after the great zetuptools purge.
Indeed, it's been fixed. Yay!