-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to detect version #797
Comments
Build output with SETUPTOOLS_SCM_DEBUG seems required It's possible related to a git repo user trust mitigation (where git intentionally stops working when uids missmatch) |
|
hah, "dubious ownership"... |
That one is extra fun, i recommend configuration of git so that it can work |
That fixed it on the buster machine. Now I have to find out why it does not happen on bullseye (or stretch), which both "just work". |
Could setuptools_scm fail earlier and output the msg from git? |
That's planned, but I'm currently a bit stretched |
@ThomasWaldmann can we verify if this works with the current switch to use |
If you tell me what to do precisely, sure. I could not find docs about this. |
@ThomasWaldmann with the current release it should work out of the box, if it doesn't I'll have to dig way deeper |
So you mean I shall retry with setuptools_scm 7.1.0 and without the fix/workaround from #797 (comment) ? |
Yes |
is this still a issue? |
I retried with setuptools_scm 7.1.0, without the workaround and it just worked. So guess this can be closed. |
Thanks for fixing it! |
Did something that was fixed already break again for this?
I have a debian buster vagrant machine that throws the "unable to detect version" now and it used to always work.
A debian bullseye vagrant machine with a very similar setup works.
borgbackup/borg#7224 this is the code I used (see Vagrantfile).
BTW: on misc. ubuntu dists this is broken since a longer while.
Traceback from the buster machine:
The text was updated successfully, but these errors were encountered: