It looks like rosdep is broken (again). We have users here who depend on being able to set up new accounts and machines on a regular basis, and this is setting back time-cortical work (prepping robots to ship to ICRA and ROSCon).
Will we be required to delete our sources ( /etc/ros/rosdep/sources.list.d ) and re-initialize them when this is over?
Thanks,
-Austin
On Apr 22, 2013, at 9:15 AM, Dirk Thomas <
dthomas@osrfoundation.org> wrote:
> Today I will start rolling out the new rosdistro files and implementation (REP 137).
> This will include the following actions:
>
> * freeze current state of rosdistro files https://github.com/ros/rosdistro
> * please do not send further pull requests since they can not be applied to the new format anyway
> * stop running the build farm, prerelease and rosinstall generator website
> * verify that the generated new rosdistro files are consistent and complete
> * replace the old rosdistro files with the new ones
> * release all affected tools (buildfarm, jenkins_scripts, jenkins_tools, prerelease_website, rosinstall_gen, rosdep, roslocate)
> * deploy them to the servers
> * restart and check all services one-by-one
>
> During the roll out period I am doing my best to keep disruption of services short.
>
> After the roll out I will send another email with updates.
> Users can expect to update at least rosdep and vcstools (since it should be the only tools they are affected by).
>
> Sorry for any inconvenience this causes.
>
> --
>
> Dirk Thomas
> ROS Development Team
> dthomas@osrfoundation.org
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
(text/plain)