http://svnweb.mageia.org/packages/updates/1/python-virtualenv/releases/1.6.4/2.mga2/SOURCES/virtualenv?revision=149032&view=markup has several bugs: - arguments passed to the Python command must be quoted correctly. $* -> "$@" - `import virtualenv` uses the very first virtualenv module it find on sys.path. This may not be the correct one. This should use pkg_resources as usual. If you want to keep this shell-script, include the original script `virtualenv` as a here-file.
Hi, thanks for reporting this bug. Assigned to the package maintainer.
Keywords: (none) => TriagedAssignee: bugsquad => levSource RPM: (none) => python-virtualenv
CC: (none) => h.goebel
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED. @ Lev, Hi, you're new to me :) Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
CC: (none) => marja11
I modified the installation to rename the pkg_resources-generated script and invoke it from /usr/bin/virtualenv. Rebuilt package available in 1/core/updates_testing (but I don't know whether we want to put it into production because of bug #3358).
Status: NEW => ASSIGNED
(In reply to comment #3) > I modified the installation to rename the pkg_resources-generated script and > invoke it from /usr/bin/virtualenv. Rebuilt package available in > 1/core/updates_testing > (but I don't know whether we want to put it into production because of bug > #3358). assigning to QA, I think that is better than to leave the package in updates/testing forever
CC: (none) => levAssignee: lev => qa-bugs
Well, according to comment #3 the packager is not sure we should push it, so I don't think QA must test it yet.
CC: (none) => stormi
It is a little early for QA to become involved with this Marja, sorry. Lev, the maintainer appears to think this conflicts with settings from bug 3358. Until he has made the decision to push this then we can't really validate it. If this is not to be pushed then it could be removed from updates testing until such time as Lev has resolved the issues he is having with this package. He can then assign to QA and ask for testing/validation and for it to be pushed to updates. Assigning back to Lev until this is ready and adding QA to cc.
CC: (none) => qa-bugsAssignee: qa-bugs => lev
Oops snap!
Source RPM: python-virtualenv => python-virtualenv-1.6.4-3.mga1.src.rpm
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
This is still valid for Mageia 2. @lev: Since you removed setting PYTHONDONTWRITEBYTECODE in cauldron (see bug 3358 comment 14), I assume this one is fixed for cauldron, too. If this is correct, feel free to close this bug.
Version: 1 => 2
Closing as per Harmut..
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED