bundled dep tarballs not used if... if some of the .egg's are already found on the system? #164
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#164
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?
Mike Booker ran "easy_install allmydata-tahoe". The second time he ran it, it outputted the following, which suggests that the bundled dependency tarballs are missing from the allmydata-tahoe.tar.gz or else there is something else preventing easy_install from using them:
I tried to reproduce this, and on my machine it worked. Here is output from "easy_install -v allmydata-tahoe" which indicates that it is using the bundled tarballs, and not searching the Internet at all.
So I wonder why this didn't work for Mike? I know, I'll ask Mike to delete his c:\Python25\Lib\site-packages\allmydata-tahoe* and try again and capture the output...
Meanwhile, I'm bumping this ticket to v0.7 milestone.
Argh, here is the logfile again with eols in place:
A-ha. If I run "easy_install allmydata-tahoe" a second time, when there is already an allmydata-tahoe .egg present, then I get these warnings, and it starts searching the Net for nevow packages:
Hm. And now I tried it on my Mac and also got it searching the internet and downloading nevow when it didn't have to...
bundled dep tarballs not used in easy_install on win32to bundled dep tarballs not used if... if some of the .egg's are already found on the system?We need to choose a manageable subset of desired improvements for v0.7.1, scheduled for two week hence, so I'm bumping this one into v0.7.2, scheduled for mid-December.
I suppose this counts as 'packaging'..
This has been fixed. I don't remember exactly which change fixed this -- perhaps changeset:c3a265839c3e2459 or changeset:faad785859ca53c5.