On Mon, Jun 4, 2012 at 12:34 PM, Jack O'Quin <
jack.oquin@gmail.com> wrote:
> On Sun, Jun 3, 2012 at 11:13 PM, Jack O'Quin <jack.oquin@gmail.com> wrote:
>> On Sun, Jun 3, 2012 at 3:16 PM, Tully Foote <tfoote@willowgarage.com> wrote:
>>> Hi Jack,
>>>
>>> Looking at the commit messages for your metadata it looks like you're using
>>> the old release create.py script for fuerte. There's a new procedure for
>>> releasing into fuerte. http://www.ros.org/wiki/release/Releasing
>>
>> I used rosrelease-legacy version 0.2.6.
>>
>> Is that not recent enough?
>
> What do the commit messages show? Do I need to make a new release with
> a more recent rosrelease version than 0.2.6?
It looks like rosrelease 0.2.6 is already the latest version:
$ pip search rosrelease
rosrelease - ROS stack release support
INSTALLED: 0.2.6 (latest)
> I would like to determine the root cause of this failure, so we can
> document how to do releases properly in the future. If it's just a
> matter of updating rosrelease, we can document the minimum version
> number on the wiki page. If it is something else, we need to figure
> out how to prevent it.
--
joq