On Tue, Dec 20, 2016 at 7:06 PM, Martin Sivak <[email protected]> wrote: >> We expect developers to install tox from pip. We documented this on >> ovirt.org: > > Not good enough, this should be mentioned in the README somewhere with > all the other dependencies (even the automation list is now too > complicated with all the lago stuff in it).
Send a patch to the readme? > Btw, I am not tainting my system using pip/easy_install if I can avoid it. I think that pip is available on CentOS. >> python-tox-2.3.1-1.el7 is available in CentOS OpsTool SIG: >> http://cbs.centos.org/koji/buildinfo?buildID=13867 > > This is much better solution, thanks. Especially because CentOS is the > officially supported OS for vdsm. I develop on Fedora and test on RHEL, so this package does not help me. > > > Martin > > > On Tue, Dec 20, 2016 at 5:46 PM, Nir Soffer <[email protected]> wrote: >> On Tue, Dec 20, 2016 at 6:01 PM, Martin Sivak <[email protected]> wrote: >>> Hi, >>> >>> I am trying to verify my patch for VDSM and that involves make check. >>> That command fails with: >>> >>> Error: cannot run tox, please install tox 2.5.0 or later >>> >>> But there is no such package available for my workstation it seems. I >>> can install python-tox, but RHEL 7+EPEL only ships with version 1.4.2. >> >> We expect developers to install tox from pip. We documented this on >> ovirt.org: >> >> easy_install pip >> pip install tox >> >> We require this for long time for tox 2.1.1. >> >> Nir >> >>> >>> Installed Packages >>> Name : python-tox >>> Arch : noarch >>> Version : 1.4.2 >>> Release : 8.el7 >>> Size : 258 k >>> Repo : installed >>> From repo : epel >>> >>> >>> -- >>> Martin Sivak >>> SLA / oVirt >>> _______________________________________________ >>> Devel mailing list >>> [email protected] >>> http://lists.ovirt.org/mailman/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
