[ros-release] build farm not resolving PIP dependencies?

William Woodall william at osrfoundation.org
Sat Sep 14 01:20:11 UTC 2013

That's a bug in the devel job it is assuming that the keys it resolves are
for apt-get, but when we fix that, and the devel passes you'll never be
able release that as we cannot build debians for things that depend on
non-debian dependencies.

On Fri, Sep 13, 2013 at 6:13 PM, Jack O'Quin <jack.oquin at gmail.com> wrote:

> Mike Purvis and I are working on a new roslint package implementation.
> That package wants to depend on cpplint, a PIP package defined in rosdep as
> python-cpplint:
>  https://github.com/ros/roslint/issues/6
> <http://jenkins.ros.org/job/devel-hydro-roslint/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=devel/2/console>
> $ rosdep resolve python-cpplint
> #pip
> cpplint
> But, the build farm tries to install it using apt-get, instead:
> http://jenkins.ros.org/job/devel-hydro-roslint/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=devel/2/console
> How can we get Jenkins to load this dependency correctly?
> Is this a bug in jenkins_scripts?
> --
>  joq
> _______________________________________________
> ros-release mailing list
> ros-release at lists.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release

William Woodall
ROS Development Team
william at osrfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20130913/fe284343/attachment.html>

More information about the ros-release mailing list