Steps to cancel already-released packages

asked 2013-08-10 20:35:21 -0600

10937 ●203 ●339 ●330 http://www.linkedin.co...

updated 2014-01-28 17:17:37 -0600

ngrennan
1 ●1 ●1

For a set of packages / a meta package that we already released into buildfarm (openrtm_common), we've figured out that we want to split it into multiple smaller sets / meta packages and fresh release each of them (for better modularity and moreover for easier handling of buildfarm error currently happening).

What step should we take before releasing the new sets of packages?

I'm afraid releasing new sets would cause conflicts if there already exist packages of the same names. Some packages have already been built and available on .deb binary repository. And just cancelling the commits for release.yaml on rosdistro seems not sufficient either.

Thanks!

edit retag flag offensive close merge delete

Comments

This question is advanced enough you should ask on the ros-release mailing list. https://code.ros.org/mailman/listinfo/ros-release

Chad Rockey ( 2013-08-11 09:01:55 -0600 )edit

Oh, okay, I'll do that. But just as a note, I see *ros.org sites come way earlier in Google's search result even when I logged off my Google account (to disable personalized search). So I prefer asking here for better searchability for the future.

130s ( 2013-08-11 14:24:36 -0600 )edit

add a comment

answered 2013-08-11 21:23:22 -0600

tfoote

58457 ●128 ●550 ●526 http://www.ros.org/

All you need to do is update the release.yaml file.

We've designed the system to be as stateless as possible. The buildfarm will do a best effort build of what's in the release.yaml. It can handle upgrades, rollbacks, additions and removals.

Conflicts with past and future packages are not a problem. It will propagate through the various stages of the build pipeline only in a self consistent state. So as long as the release.yaml doesn't have conflicts the debs should not either.

Note this does not absolve you of considering your users and providing good communication with respect to the development model. Your users should know what's going on and depending on the development state of the package. If there are expectations of stability for your users the buildfarm will not prevent you from breaking compatibility.

Comments

Thanks for the explanation, and also for the one-stop service; that sounds super nice and easy to use!

130s ( 2013-08-12 04:05:40 -0600 )edit

add a comment

Steps to cancel already-released packages

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

Steps to cancel already-released packages edit

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

Steps to cancel already-released packages