I believe there is a cleaner solution for doing the syncronization.
However I'm holding off on implementing it until Fuerte is out the door so
debugging the new syncronization method doesn't interfere with the pending
release.
Tully
On Fri, Apr 20, 2012 at 1:57 PM, Ken Conley <
kwc@willowgarage.com> wrote:
> To add, it's a condition that doesn't happen very frequently, and
> would take a lot of extra infrastructure to support.
>
> I was thinking of sending an e-mail to ros-release yesterday to ask
> that people hold off from doing Fuerte releases right now so that we
> can spin the final RC, which is related to the above error condition
> that you saw. Basically, this RC week is not a good week to be doing
> releases. I decided not to as we can ultimately deal with it, but you
> will see conditions like the above more often because we have to sync
> much more often.
>
> - Ken
>
> On Fri, Apr 20, 2012 at 1:53 PM, Wim Meeussen <meeussen@willowgarage.com>
> wrote:
> >> Would it be possible to delay the prerelease builds in that case until
> the
> >> main debs are built, and send a warning email instead of failing? I
> guess
> >> that could save some useless cycles in setting up the prereleases all
> over
> >> again.
> >
> >
> > That is pretty much what the prerelease test does. To do this check it
> needs
> > to first download the stack(s) that you are testing, find out what their
> > dependencies are, and then query the apt repository for these
> dependencies.
> > Instead of running these checks from a hudson node in a chroot
> environment,
> > we could run them on the server that creates prerelease jobs. However,
> that
> > approach would not scale very well when the number of requests goes up.
> > Wim
> >
> >
> > --
> > --
> > Wim Meeussen
> > Willow Garage Inc.
> > <http://www.willowgarage.com)
> >
> > _______________________________________________
> > Ros-release mailing list
> > Ros-release@code.ros.org
> > https://code.ros.org/mailman/listinfo/ros-release
> >
> _______________________________________________
> Ros-release mailing list
> Ros-release@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-release
>
--
Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote@willowgarage.com
(650) 475-2827
(text/plain)