[ros-release] Is there a reason why dependencies get broken so often with ROS packages?

[Tully Foote]

Hi Jon,

Can you clarify a little bit more about what you mean about conflicting
dependencies? The only known issues have been related to upstream debian
packages we depend upon which have changed.

Also if you are on shadow-fixed this is possible as we sometimes roll back
releases in that repo.

And as Mike mentioned dist-upgrade is required if there are new
dependencies added.

I don't know of anything in the ROS release system itself has nothing
inherently causing conflicts except that it's very active with a large user
base making many releases.

If you have some examples we can take a closer look at what caused them.

Tully


On Fri, May 23, 2014 at 11:08 AM, Mike Purvis <mpurvis at clearpathrobotics.com
> wrote:

> I've sometimes had issues like this which are resolvable with a
> dist-upgrade— that seems most reliable for getting the system to an overall
> known state.
>
>
>
> On 23 May 2014 11:50, Jonathan Bohren <jonathan.bohren at gmail.com> wrote:
>
>>  I've noticed over the last year or so that if someone goes a few weeks
>> or months without upgrading their installed debian packages on ubuntu that
>> they run into problems with conflicting dependencies. Is this a known
>> problem and if so, is it caused by anything particular with the ROS release
>> infrastructure?
>>
>> -j
>>
>> --
>> Jonathan Bohren
>> Laboratory for Computational Sensing and Robotics
>> http://dscl.lcsr.jhu.edu/People/JonathanBohren
>>
>>
>> _______________________________________________
>> ros-release mailing list
>> ros-release at code.ros.org
>> http://lists.ros.org/mailman/listinfo/ros-release
>>
>>
>
> _______________________________________________
> ros-release mailing list
> ros-release at code.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20140523/97c5526d/attachment.html>