As a quick workaround, you can add 'pip' in the list of packages of your manifest.
If the Python crowd needs to be able to choose between pip and pip3, I would even rather make that the official behavior. Sylvain On Fri, Oct 20, 2017 at 8:48 AM, Dennis Hemker <dennis.hem...@dfki.de> wrote: > Additionally, as this problems appears, it would be an advantage to control > whether to use pip or pip3 > > Am 20. Oktober 2017 12:12:16 MESZ schrieb Sylvain Joyeux > <bir.sylv...@gmail.com>: >> >> Autoproj should have installed the python-pip Ubuntu package. Could >> you verify this ? >> >> On Fri, Oct 20, 2017 at 7:04 AM, Dennis Hemker <dennis.hem...@dfki.de> >> wrote: >>> >>> Hey, >>> >>> I added some pip dependencies to my package set and autoproj tries to >>> install them. Running a full-bootstrap on the build server, I observed >>> that >>> autoproj wants to install the pip packages, but does not make sure that >>> pip >>> itself is installed. Output is: >>> >>> installing/updating Python dependencies: scikit-learn, scipy >>> Command failed >>> autoproj: failed in osdeps phase >>> command 'pip' not found >>> see >>> >>> <http://buildsrv01:8080/job/entern/Flavor=rock-15.05,node=Ubuntu_16.04/ws/dev/install/log/autoproj-osdeps.log> >>> for details >>> Build step 'Execute shell' marked build as failure >>> >>> >>> Best, Dennis >>> >>> ________________________________ >>> >>> Rock-dev mailing list >>> Rock-dev@dfki.de >>> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev >> >> > > _______________________________________________ > Rock-dev mailing list > Rock-dev@dfki.de > http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev > _______________________________________________ Rock-dev mailing list Rock-dev@dfki.de http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
