Incorrect pycryptopp architecture selected on osx 10.6. #1006
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#1006
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?
My osx 10.6 box has python2.6 and an Intel Core 2 Duo, yet when I follow the installation instructions, it appears that the pycryptopp egg is for the wrong version of python, and perhaps the wrong instruction set.
Notice it refers to "py2.5" inside the 2.6 site-packages directory.
Attached full install and unittest logs.
Attachment tahoe-lafs-1.6.1.build.log (30227 bytes) added
build log
Attachment tahoe-lafs-1.6.1.test.log (64420 bytes) added
test log
Notice, #1005 also refers to the same commands and output. The first exception in the test output is a twisted problem documented in #1005 and is not related to this issue.
I would like to investigate this, but I already have a full load of other Tahoe-LAFS tickets for v1.7.0 Milestone. If anyone else wants to help out that would be great.
I suspect this was a bug in older versions of Mac OS X tools, the version of Python that came with Mac OS X, etc. I'm closing this on the assumption that it is no longer relevant, and someone will need to re-open it if it recurs.