-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Installation issues on Travis CI #345
Comments
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): The changes between 12.0.5 and 12.1 were trivially small. I would be surprised if the 12.1 release was a regression from 12.0.5. Do you have reason to believe that (a) the issue did not exist with setuptools 12.0.5 and (b) the bootstrap-buildout has not changed? |
Original comment by Anonymous: I am not sure about 12.0.5, but I am sure that 12.0.4 was working: https://travis-ci.org/bioidiap/bob.core/jobs/48035636 |
Original comment by Anonymous: And I am sure that I haven't changed the bootstrap-buildout.py file (which is still up to date, I have double-checked that). On the other hand, I am not 100% sure that Travis hasn't updated their system, though I didn't receive a notification... |
Original comment by znerol (Bitbucket: znerol, GitHub: znerol): Related issue on travis issue tracker. |
Original comment by Anonymous: Indeed, it seems to be an issue with the pre-installed setuptools, which I can reproduce locally.
So far, my workaround is to use the
However, we would need to update the travis configuration files each time that they update their system. Since we have more than 40 packages: The solution in the travis issue tracker would probably work as well, but as it is written there, this is a work-around and no fix. Again, I don't know how long this solution will work. |
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): The issue reported in the travis bug tracker is slightly different, displaying a VersionConflict prior to the AttributeError:
|
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): I think I now know what's happening. In ez_setup.use_setuptools, which is invoked by buildout's bootstrap, the code will use pkg_resources to determine if the installed setuptools is a suitable version. If it is not, it unloads pkg_resources (using |
Original comment by Anonymous: I am currently re-running the tests. I'll let you know. |
Original comment by Anonymous: Yes, I can confirm that the tests are running now, both on Travis and using the local virtualenv. Thank you very much for fixing this issue! |
Original comment by tseaver (Bitbucket: tseaver, GitHub: tseaver): Clears up buildout/buildout#237, too. Thanks, @jaraco! |
Originally reported by: Anonymous
Since the upload of version setuptools version 12.1 yesterday, our builds on Travis start to fail:
https://travis-ci.org/bioidiap/bob.core/jobs/50389380
Using the latest bootstrap-buildout.py, we get the following error message:
Interestingly, lines 81 and 82 of
pkg_resources/__init__.py
(the imports of the _vendor module) pass, but not the actual use of it.Sorry for not being able to supply more information...
Could you please double-check, what might be going on?
Thank you
Manuel
The text was updated successfully, but these errors were encountered: