Description of problem: OpenStack actively uses pip -c flag [1] for controlling dependencies for its tests. However, the current virtualenv in Fedora 23 embeds pip 6.0.8 which does not support it. Meaning, that all people working on OpenStack on Fedora will have to update virtualenv itself via "sudo pip install". I wonder if it's possible to provide a system update to at least 13.1 (featuring pip 7.1) [2]. Thanks! [1] https://pip.pypa.io/en/stable/user_guide/#constraints-files [2] https://virtualenv.pypa.io/en/latest/changes.html#id11
Upgrading in a released version is not acceptable by update policy. Fedora 24 contains virtualenv-14.0 dnf --releasever=24 update python-virtualenv will pull that specific package (and dependencies) from f24 repositories.
Could you point me to this update policy banning virtualenv? Cause other packages easily upgrade on a released version, even bumping major version.
ah, sorry. https://fedoraproject.org/wiki/Updates_Policy#Stable_Releases
I don't see an explicit "no never" in this link, but I guess I can't argue. It's just sad for me to redirect people to ubuntu as OpenStack development platform again...
(In reply to Dmitry Tantsur from comment #2) > Could you point me to this update policy banning virtualenv? Cause other > packages easily upgrade on a released version, even bumping major version. I guess it also depends on the maintainer(s) - sometimes they feel that the fallout of a major upgrade is manageable while others try stay on the safe side. E.g. ansible recently got upgraded to 2.0 in Fedora (and so far it works for me without any problems). Other times we're not so lucky (e.g. botched hamster 2.0 upgrade in F23) so being cautious on major upgrades seems to a be a good thing.
Also note that we have inconsistency between shipped pip's: system on is 7.1 (which works), virtualenv one is 6.0.8.
@dmitry: it's mentioned in https://fedoraproject.org/wiki/Updates_Policy#Beta_to_Pre_Release * Avoid Major version updates, ABI breakage or API changes if at all possible. https://fedoraproject.org/wiki/Updates_Policy#Philosophy mentions this as well: ... As a result, we should avoid major updates of packages within a stable release.
I don't think virtualenv follows semver (like Firefox), so I don't think this applies. Major version bump seems to designate updating of bundled libraries to major versions. In 13.1 these are: pip to 7.1.0, setuptools to 18.0.1. In Fedora we have (surprise!) pip 7.1.0, setuptools 18.0.1. So we should have had virtualenv 13.1 to avoid confusion.