Hello Andrei,I was not aware of that. I'm using https://www.redhat.com/archives/avocado-devel/2017-January/msg00020.html (with some additions) so I'll take a look into what can be done to improve this. We partially dived into this area with Jan Sčotka who is using Avocado and is looking for RPMs for dependencies and we don't have the capacity to maintain a repo of them, but if pip should not be used as root then we'll have to probably create a script to fetch the latest versions from brew, rebuild it on all needed archs and publish it into some downstream repo. Ideally we should share this effort among multiple teams.
Lukáš Dne 1.2.2017 v 17:48 Andrei Stepanov napsal(a):
Hello. We are currently experiencing some issues with avocado / avocado-vt. Our automation can be described in next steps: 0. Install RHEL 6/7. 1. Clone "master" branches for avocado/avocado-vt from github. 2. In avocado dir: make requirements python setup.py install 3. In avocado-vt dir: make link pip install sphinx pip install -r requirements.txt python setup.py install 4. Run tests. Above commands are run from root account. We cannot use this approach any more. It doesn't work with RHEL7.3. I have opened a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1417613 Than I had discussion with Tomas Orsava. The problem is, running pip as root in Fedora/EPEL is not supported and will break your system. https://fedoraproject.org/wiki/Changes/Making_sudo_pip_safe My question is: what is official way to install avocado/avocado-vt? Invoking pip commands from root account is a bad approach. Is there a safe way to install avocado & avocado-vt?
signature.asc
Description: OpenPGP digital signature
