Confirmed; it was broken with the old version of rosdep, but it's 
working again with the latest version.

As a note, this update breaks the PR2 stable releases that were packaged 
as DVD images, since required files are now missing from github. For 
those of us trying to deliver production-quality robots on top of ROS, 
this is unacceptable.

-Austin

On 04/22/2013 08:00 PM, Dirk Thomas wrote:
> You have been using two incompatible versions of "rosdep" and 
> "rosdistro" during the roll out phase.
> Please make sure to update all packages as mentioned in the second 
> announcement email 
> (https://code.ros.org/lurker/message/20130423.025734.7689bd35.en.html).
>
> rosdep will continue to work as-is.
> It is neither necessary to delete sources nor to re-initialization the 
> cache.
>
> - Dirk
>
>
> On 22.04.2013 18:02, Austin Hendrix wrote:
>> 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
>>
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users