Fixing boost 1.50 issues while branching issues

[Dennis Gilmore]

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

El Sun, 12 Aug 2012 09:59:08 -0600
Kevin Fenzi <kevin at scrye.com> escribió:
> On Sun, 12 Aug 2012 07:43:57 -0500
> Richard Shaw <hobbes1069 at gmail.com> wrote:
> 
> > Ok, somehow I managed to do the same thing with OpenImageIO...
> > 
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=4379927
> > 
> > Although I'm pretty sure I did the build with "--target f18". Are
> > there any other options than incrementing the release and building
> > in both rawhide and f18 again?
> 
> Sorry, I was leading you wrong before... Dennis'es reply was correct. 
> 
> Builds go into f18-candidate, which also populates f18-build (the
> buildroot), then at the nightly branched compose they are moved to
> f18. 
f18-candidate is the target name and has nothing at all to do with any
tags, a target has 2 things the tag used to populate the buildroot and
the tag that resulting builds are tagged into.

Right now the f18-candidate target is setup to populate the
buildroot using f18-build and resulting builds are tagged into f18
directly. when we enable bodhi in a few days we will then adjust the
f18-canidate target to tag the resulting builds into
f18-updates-candidate.

> 
> Don't worry about what tag something is in? It works just like rawhide
> does right now. You can build, wait for the buildroot to update and
> build the next dependent package. 

koji list-targets (with some filtering)
Name                           Buildroot                      Destination                   
- ---------------------------------------------------------------------------------------------
f18                            f18-build                      f18                           
f18-candidate                  f18-build                      f18

f18 and f18-candidate both do exactly the same thing.

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

iEYEARECAAYFAlAowvcACgkQkSxm47BaWff23wCgmgOKyiF/LlRj71elbNRQa9F9
VTEAoJbPeFVDBn/Ra5posDiOR0Gx9DUT
=BAp4
-----END PGP SIGNATURE-----