versioning issue

[ThomasWaldmann]

vancheese says:

I'm having issues with the version numbers as it appears the forking results in a version which is rejected by version.py module.

(add steps how to reproduce this problem)

Is there a way to override/define the version in the pyproject.toml so I can test the documentation etc using the latest git version?

Originally posted by @vancheese in #8550 (comment)

[vancheese]

Steps to reproduce

1. fork borgbackup repo to a personal repo
2. Checkout repo
3. enter local repo
4. virtualenv --python=$(which python3) borg-env
5. source borg-env/bin/activate
6. pip install -r requirements.d/development.txt
7. pip install -r requirements.d/docs.txt
8. pip install -e .
9. borg -v

File "/home/andy/Documents/Repos/borg/src/borg/version.py", line 24, in parse_version
raise ValueError("Invalid version string %s" % version)
ValueError: Invalid version string 0.1.dev8904+g84744ac.d20241215

[ThomasWaldmann]

How did you do 1. and 2.?

What does git tag output?

[vancheese]

1. was a Github fork
2. was a standard git clone

git tag returns nothing

[ThomasWaldmann]

git tag returns nothing

git fetch --tags should fix the issue, then pip install -e . again.

[vancheese]

Yeah, that fixed everything, sorry about that and thanks

[ThomasWaldmann]

If you like, check our developer docs and maybe add better instructions there.