ImportError: No module named setuptools_darcs.setuptools_darcs #1054
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#1054
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?
On the test-clean builder:
http://tahoe-lafs.org/buildbot/builders/clean/builds/2303/steps/test-desert-island/logs/stdio
The attached patch works-around this by commenting-out the requirement to have
setuptools_darcs
at build-time. The drawback of this approach is that if someone builds a distribution, e.g. a source distribution by runningpython setup.py sdist
, then they have to manually installsetuptools_darcs
first. If they don't, then the resulting distribution will be incomplete -- it will be missing all files that aren't part of the allmydata Python package-directory, such as docs and .xhtml files for the WUI.I get this error if I try to install Tahoe-LAFS using distribute-0.6.14, like so:
…
This is caused by a bug in Distribute: https://bitbucket.org/tarek/distribute/issue/55/revision-control-plugin-automatically-installed-as-a-build-dependency-is-not-present-when-another-build-dependency-is-being
Attachment no-build-require-setuptools_darcs.darcs.patch (15297 bytes) added
This patch is needed to fix #668 (easy_install allmydata-tahoe is broken).
Will review tomorrow.
Here is an alternative which avoids the failure mode of people building broken distributions at the cost of bundling a copy of
setuptools_darcs
with Tahoe-LAFS.Attachment ticket1054-bundle-setuptools_darcs.darcs.patch (33356 bytes) added
Looks good. I'll combine the first and third patches when pushing this to trunk.
In changeset:0fb49375c0365e0a:
In changeset:4cba75e000ba1b16:
This error is still happening in this install-to-egg step:
http://tahoe-lafs.org/buildbot/builders/Josh%20ubuntu-amd64%20laptop/builds/26/steps/install-to-egg/logs/stdio
which is a build of r4941, after the above two patches.
It appears from the line
that this may have something to do with setuptools_trial. But setuptools_trial is going away if #1296 is fixed, so maybe this error will too.
The error on the Josh ubuntu-amd64 has gone away now that I uploaded a new version of
setuptools_trial
setuptools_trial-0.5.12, which doesn't requiresetuptools_darcs
.