[ros-users] Rerelease of all compiled Hydro and Indigo packages expected

Tully Foote tfoote at osrfoundation.org
Thu May 22 22:33:07 UTC 2014

HI Everyone,

We identified an issue with 0.5.8 when releasing into Oneiric. It does not
support the new build format (Upstream ticket:
https://github.com/ros-infrastructure/bloom/pull/279). So bloom version
0.5.9 now special cases oneiric to use the old system. (Which has correct
build flags)

This only effects groovy releases. If you made a release with 0.5.8 into
groovy this week you will need to rerelease using 0.5.9. And going forward
make sure to use bloom 0.5.9 for future groovy releases.

Thanks for you patience and thank you to the many maintainers who have
already rereleased hydro and indigo. We have made a lot of progress in
rereleasing hydro and groovy packages.


On Tue, May 20, 2014 at 6:31 PM, Tully Foote <tfoote at osrfoundation.org>wrote:

> Hi Everyone,
> We've identified an issue with the ROS debian packages on Quantal Raring
> and Trusty and will be working with the maintainers to resolve the issue in
> the next week. We hope to have updated packages available at the end of the
> week. This update will have noteable performance implications on the
> effected platforms platforms.
> For more information please see the email sent to the maintainers below.
> PS Maintainers if this is the first time you are getting this email.
> Please sign up for ros-release at lists.ros.org
> Tully
> Message sent to ros-release:
> Hydro and Indigo maintainers,
>> What's needed:
>> If you have released a compiled package into either Hydro or Indigo we
>> highly recommend reblooming the package after upgrading bloom to 0.5.8 or
>> higher. For packages to be fixed they must be processed by the new version
>> of bloom with a debian increment. ***It is not required to change the
>> upstream repository! Only to rerun bloom on the release repository ***
>> What's this about:
>> We discovered that debhelper, the tool that we use for building debians,
>> stopped automatically adding the recommended compile flags for debian
>> packages in Quantal, Raring and Trusty for debian packages with compat
>> version 7 which is what we've been releasing. This means that the binaries
>> do not have -g or -O2 so neither debug symbols nor optimization.
>> There are packages where an order of magnitude slowdown has been observed
>> due to the lack of optimization.
>> What we changed:
>> We have changed the compat version to version 9 which will get the
>> default flags again. This has been done in the template used by bloom.
>>  With the new version of bloom(0.5.8) all packages will be built with
>> compat 9.
>> Links to the relevant discussions:
>> Initial ticket:
>> https://github.com/ros-infrastructure/buildfarm/issues/197
>> Bloom issues: https://github.com/ros-infrastructure/bloom/issues/277
>> Bloom patch: https://github.com/ros-infrastructure/bloom/pull/278
>> How to fix your package(s):
>>  * Make sure to update bloom to 0.5.8 (available from apt)
>>  * for each repo you maintain run `bloom release MY_REPO -t ROSDISTRO -r
>>    * This will rerun bloom and build debians X.Y.Z-1 assuming previously
>> they were X.Y.Z-0 previously.
>> Bloom will submit the pull request like usual and with the reblooming
>> your package will get the new template.
>> Indigo Beta ramifications:
>> We are very close to our beta release of Indigo but with this discovery
>> that our LTS platform is missing build flags we will delay the beta until
>> most packages have been rereleased.
>> Thanks ahead of time for taking care of this. I hope it will only take
>> each of you a few minutes. This is going to cause a lot of building on the
>> farm and I've turned on a lot of executors ahead of time to speed things
>> up. If at all possible it would be great to get these rereleases done this
>> week.
>> Tully
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20140522/1ec145a6/attachment.html>

More information about the ros-users mailing list