[Ros-release] Debian source build failed -- what to do?

Weißhardt, Florian Florian.Weisshardt at ipa.fraunhofer.de
Tue Jun 5 14:29:44 UTC 2012

Hi Jack and Tully,

just to add to that discussion: we figured out the same thing while releasing the same code in both electric and fuerte using the same revision number. A workaround for us was to always increase the version number and triggering new releases for electric and fuerte directly after each other. Because a later update for just one ROS release didn't work.

I think the use case of having the same code released for two (or even more) ROS releases under the same version number is not so rare.


-----Original Message-----
From: ros-release-bounces at code.ros.org on behalf of Tully Foote
Sent: Mon 6/4/2012 8:46 PM
To: Jack O'Quin
Cc: ros-release at code.ros.org
Subject: Re: [Ros-release] Debian source build failed -- what to do?
Hi Jack,

I've figured out the problem.  You're attempting to release 0.4.2 into
fuerte which is already released in electric. When the release script
detected that the tarball was already present, it returned incorrectly
before updating the yaml file.  I think you're the first person using the
two toolchains together on the same revision number.  I've released
rosrelease 0.2.7 which should work now.


On Mon, Jun 4, 2012 at 10:37 AM, Jack O'Quin <jack.oquin at gmail.com> wrote:

> On Mon, Jun 4, 2012 at 12:34 PM, Jack O'Quin <jack.oquin at gmail.com> wrote:
> > On Sun, Jun 3, 2012 at 11:13 PM, Jack O'Quin <jack.oquin at gmail.com>
> wrote:
> >> On Sun, Jun 3, 2012 at 3:16 PM, Tully Foote <tfoote at 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

Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote at willowgarage.com
(650) 475-2827

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20120605/2a0bb449/attachment-0009.html>

More information about the Ros-release mailing list