<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: [Ros-release] Debian source build failed -- what to do?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi Jack and Tully,<BR>
<BR>
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.<BR>
<BR>
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.<BR>
<BR>
Best,<BR>
Florian<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: ros-release-bounces@code.ros.org on behalf of Tully Foote<BR>
Sent: Mon 6/4/2012 8:46 PM<BR>
To: Jack O'Quin<BR>
Cc: ros-release@code.ros.org<BR>
Subject: Re: [Ros-release] Debian source build failed -- what to do?<BR>
<BR>
Hi Jack,<BR>
<BR>
I've figured out the problem. You're attempting to release 0.4.2 into<BR>
fuerte which is already released in electric. When the release script<BR>
detected that the tarball was already present, it returned incorrectly<BR>
before updating the yaml file. I think you're the first person using the<BR>
two toolchains together on the same revision number. I've released<BR>
rosrelease 0.2.7 which should work now.<BR>
<BR>
Tully<BR>
<BR>
On Mon, Jun 4, 2012 at 10:37 AM, Jack O'Quin <jack.oquin@gmail.com> wrote:<BR>
<BR>
> On Mon, Jun 4, 2012 at 12:34 PM, Jack O'Quin <jack.oquin@gmail.com> wrote:<BR>
> > On Sun, Jun 3, 2012 at 11:13 PM, Jack O'Quin <jack.oquin@gmail.com><BR>
> wrote:<BR>
> >> On Sun, Jun 3, 2012 at 3:16 PM, Tully Foote <tfoote@willowgarage.com><BR>
> wrote:<BR>
> >>> Hi Jack,<BR>
> >>><BR>
> >>> Looking at the commit messages for your metadata it looks like you're<BR>
> using<BR>
> >>> the old release create.py script for fuerte. There's a new procedure<BR>
> for<BR>
> >>> releasing into fuerte. <A HREF="http://www.ros.org/wiki/release/Releasing">http://www.ros.org/wiki/release/Releasing</A><BR>
> >><BR>
> >> I used rosrelease-legacy version 0.2.6.<BR>
> >><BR>
> >> Is that not recent enough?<BR>
> ><BR>
> > What do the commit messages show? Do I need to make a new release with<BR>
> > a more recent rosrelease version than 0.2.6?<BR>
><BR>
> It looks like rosrelease 0.2.6 is already the latest version:<BR>
><BR>
> $ pip search rosrelease<BR>
> rosrelease - ROS stack release support<BR>
> INSTALLED: 0.2.6 (latest)<BR>
><BR>
> > I would like to determine the root cause of this failure, so we can<BR>
> > document how to do releases properly in the future. If it's just a<BR>
> > matter of updating rosrelease, we can document the minimum version<BR>
> > number on the wiki page. If it is something else, we need to figure<BR>
> > out how to prevent it.<BR>
><BR>
> --<BR>
> joq<BR>
><BR>
<BR>
<BR>
<BR>
--<BR>
Tully Foote<BR>
Systems Engineer<BR>
Willow Garage, Inc.<BR>
tfoote@willowgarage.com<BR>
(650) 475-2827<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>