missing git tags causes tests to fail #2300
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#2300
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?
kaoline tried to run
setup.py test
in a tree that was cloned from zancas's github repo. This failed when something tried toimport allmydata._version
.Zancas's repo lacks tags, so kaoline's tree lacked them too.
setup.py build
ran without complaint, but it did not createsrc/allmydata/_version.py
as usual, because thegit describe --tags --dirty --always
command (copied from Versioneer) didn't see any tags, so setup.py didn't deduce a version string, so it didn't create_version.py
. This is ok for setup.py, but actually trying to use tahoe (including running tests) fails, since*init*.py
fails to do itsimport _version
.Modern Versioneer handles this better (by faking a "0.0" tag if it can't find any others). The code in tahoe's setup.py is copied from an older form of Versioneer. The best fix (after 1.11) is probably to switch over to Versioneer altogether, instead of copying fragments of it into setup.py .
Meanwhile, I'd recommend that developers start by cloning the official repo at https://github.com/tahoe-lafs/tahoe-lafs.git , which should get them all the correct tags.
I had the same problem when setting up Travis-CI, since by default it does a shallow clone (
--depth=50
IIRC). I fixed it in that case by adding agit pull --depth=1000
command to source:.travis.yml.Due to the fix for #2340, this at least now should print a reasonable warning message during the build.
Milestone renamed
renaming milestone
Moving open issues out of closed milestones.
Ticket retargeted after milestone closed