-
-
Notifications
You must be signed in to change notification settings - Fork 211
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
new version of setuptools_scm just broke my build #164
Comments
this seems to be an artifact of uploading the sdist first and the bdist-egg second please rerun the build to see if its still happens, i strongly suggest including setuptools_scm into the build im considering warning if setuptools_scm was egg/easy_installed |
We are seeing the same thing by just running: pip install -r requirements.txt. What is the workaround? 15:36:20 Complete output from command python setup.py egg_info: |
We're seeing the same thing:
|
I'm hitting this too, package only ever had a sdist created for it:
|
@RonnyPfannschmidt this happen for all the 15 builds of my build matrix: https://nine.buildbot.net/#/builders/1/builds/1707 The thing is:
Buildbot does not use setuptools_scm, but it does use lz4, which in turn uses setuptools_scm. I'd expect a couple of other projects to be in the same position. Could you please re-release a -p1 package bdist-egg first? |
workaround for pypa/setuptools-scm#164
@tardyp it seems i misinterpreted the build log, i need to investigate why the egg in your case seems to have an issue (because the setuptools_scm eggs) are build precisely to avoid such issues since your issue happens i have to presume that setuptools_scm no longer correctly works for sdists |
i can replicate the problems with
|
@RonnyPfannschmidt thanks for working on it. Reverting to 1.15.0 did fix the issue: |
updating my PR to pull git+https://github.com/pypa/setuptools_scm to see if your fix works for me. |
@tardyp master is fixed now - please tell me if you prefer i release, or if you would run against it first to verify |
looks like installing from git+https will not work
Do you have another suggestion for testing it before release? |
im preparing something |
fixes an interaction issue discovered in pypa#164
@tardyp please rerun your build, i update setuptools_scm to work from pip install via git |
ps, i removed the 1.15.3 release from pypi |
There were a temporary issue in setuptools_scm 1.15.3 [1] that broke the world. Fortunately, it has been fixed in 1.15.4 so we are allowed to use latest version once again. [1] pypa/setuptools-scm#164
Due to pypa/setuptools-scm#164 we are unable to install pytest-xdist Change-Id: I52da4b071a1c57270e7dfbbe981a8eeeb839aba1
Due to pypa/setuptools-scm#164 we are unable to install pytest-xdist Change-Id: I52da4b071a1c57270e7dfbbe981a8eeeb839aba1 (cherry picked from commit 2d594c2)
I see a similar error using a version like Note that when
|
@twall thats a new issue please open a new one |
- pin setuptools to an earlier version for < py36 (xenial) ``` File Finder Failed for .git = setuptools_scm.git:list_files_in_archive ``` - preinstalling basic layer dependencies to avoid chicken and egg issues deploying on xenial This [related](pypa/setuptools-scm#164) issue provides more context.
Please have a look at this build:
https://nine.buildbot.net/#/builders/2/builds/125578
looks like you just release setuptools_scm, so I would expect this is a problem with the new release..
The text was updated successfully, but these errors were encountered: