build failure on OS-X #2728
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#2728
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?
Tahoe trunk (git [186f6d4a59a879ee93207a48bca15fbdf2741206]) fails to build on OS-X 10.11, using python from homebrew, and a fairly minimal set of python packages installed via pip (I have: certifi, click, pip, pipsi, requests, setuptools, virtualenv, wheel).
The full log is:
I believe the specific problem is that Tahoe's current
_auto_deps.py
declares that it needs pyopenssl-0.13 or 0.13.1 (which won't compile) unless a newer version is found.If I create a virtualenv and pre-install the current version of pyopenssl into it, I get a different sort of openssl error instead:
I think this happens during the cryptography-1.2.2 build (which is odd, because cryptography-1.2.2 was already installed in the virtualenv (as a dependency of pyopenssl).
My hunch is that cryptography-1.2.2 doesn't build on vanilla OS-X 10.11 right now (because of the missing system headers), but "pip install" works because there's a pre-compiled wheel hosted on PyPI. Tahoe's zetuptoolz doesn't know anything about wheels, nor does it seem to correctly notice that the package is already installed, so it tries to rebuild it, and fails.
I think this will be resolved by #1582, but I don't know if that will help the upcoming 1.10.3 release build on OS-X.
I had a similar problem on linux (debian/sid). I created a new virtualenv (with only pip, setuptools, and wheel installed), and tried to build tahoe inside it. It failed when trying to build (old) pyopenssl-0.13.1. Manually installing pyopenssl-0.15.1 and then trying again made it past the ssl problems, but failed due to a setuptools mismatch error:
This results from cryptography-1.2.2 having a dependency upon
setuptools >= 1.0
.Again, I think #1582 will fix this, but I don't currently know how to build tahoe on a debian/sid system.
Our travis tests are passing, so there must be some linux platforms that are buildable. The buildbot's Ubuntu-15.10 "wily" builder is failing to build with 'pip' (but passing without it, possibly because of a system-provided python-openssl package).
Adding to 1.10.3 milestone in case it's a blocker.
The first error is an instance of #2474.
The second error when building pyOpenSSL looks like https://github.com/pyca/cryptography/issues/2692
The switch to pip has fixed this. We now use the current versions of all dependencies.
Milestone renamed