| Summary: | [abrt] python-virtualenv-1.5.1-1.fc14: virtualenv.py:624:call_subprocess:OSError: Command /tmp/resource/bin/python -c "#!python | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tobias Mueller <fedora-bugs> | ||||
| Component: | python-virtualenv | Assignee: | Steve Milner <smilner> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | dmalcolm, smilner | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:2026c726 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-08-16 15:51:46 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Tobias Mueller
2011-01-23 17:04:07 UTC
Created attachment 474839 [details]
File: backtrace
Thank you for the bug report Tobias. I'm going to try to reproduce this now. Tobias, Can you verify you are still seeing this happen? I just tried on F14 x86_64 with python-virtualenv 1.5.1-1. I did the following (output being hand typed as I tested on a different machine): $ cd /tmp/ $ virtualenv resource New python executable in resource/bin/python Installing setuptool...................done. $ Hm. It works for me now. Reading the backtrace, I assume that it's not hardened against network failures, i.e. 'Reading http://pypi.python.org/simple/distribute/', 'Download error: [Errno 101] Network is unreachable -- Some packages may not be found!', I guess the issue itself still exists but you don't hit it with a properly working network setup. Interesting. A possible fix would be virtualenv sensing a failure in distribute and giving a helpful error/stack trace noting that the external code is unreachable. Do you think the issue is worth the time to patch and submit? If so, I'll take a look at virtualenv and see if I can't create a patch for it when I get some free time. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |