boost 1.53 in Rawhide

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El Fri, 08 Feb 2013 10:41:29 +0100
Kalev Lember <kalevlember at gmail.com> escribió:
> On 02/08/2013 03:56 AM, Kevin Fenzi wrote:
> > On Fri, 08 Feb 2013 02:57:19 +0100
> > Petr Machata <pmachata at redhat.com> wrote:
> >> I have just built boost 1.53.  I didn't go through the side tag as
> >> originally envisioned, as tomorrow's mass rebuild should take care
> >> of it all in one fell swoop.  I'll still be available for help if
> >> your package mysteriously fails or if there's just too many <'s
> >> and >'s in your package for a sane person to wrap their head
> >> around.
> > 
> > Dennis is traveling right now, so it looks like the mass rebuild
> > may be pushed off to the 12th.
> > 
> > Do we want to untag this until then? 
> > Or is it going to cause broken deps?
> 
> The mass rebuild doesn't do rebuilds in the dep order, it just goes
> through all the packages alphabetically. With packages using boost,
> there are often long dep chains that need rebuilding in the dep
> order. I would say that it still needs some provenpackager action to
> get the rebuilds done. Petr, are you a provenpackager now?
> 
> In my opinion, it would be perfect to have the gist of the boost
> rebuilds completed by the time of the mass rebuild.
> 
> Boost has not only shared libraries, but also a lot of header-only
> template code. When provenpackagers do rebuilds, they usually take
> care of the broken library deps, but nobody rebuilds packages that
> only use the template code. If we manage to complete the library
> rebuilds by the time of the 12th, then the mass rebuilds would also
> take care of doing the rest of the rebuilds, to ensure that all
> packages are really using new boost 1.53 template code.
> 
As Kalev said the mass rebuild happens alphabetically, additionally the
results of the mass rebuild are not tagged into the buildroot. The
process is not designed to deal with soname bumps. If you can get it
done before the 12th then please do so. if not you will need to wait
until after the mass rebuild and use a side tag.

Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlEUzdIACgkQkSxm47BaWfdrVgCgjtHE5RCYkd72Zgya0DniotJT
jiMAmwcztwaWMJ1XyNT1Eo9XCTy/Q+OU
=UMO5
-----END PGP SIGNATURE-----