Package rebuilds for gcc bug https://bugzilla.redhat.com/show_bug.cgi?id=634757

[Jesse Keating]

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

On 10/5/10 3:59 PM, Mamoru Tasaka wrote:
>> To handle the F14 scene I've come up with this strategy:
>> > * For things tagged in dist-f14 and no newer build elsewhere, do a bump,
>> > build and tag directly into dist-f14.  While there is some risk of
>> > breakage, it is quite minimal and with discussion from QA we are willing
>> > to take that chance.  This work is ongoing.
>> >
>> > * For things tagged in dist-f14-updates-testing, do a bump, build and
>> > then edit the bodhi ticket to add the new build, and re-push to
>> > updates-testing.  This work will begin soon.
>> >
>> > * for things tagged in dist-f14-updates-candidate, do a bump and build.
>> >   Then look for an open bodhi ticket for that package, adjusting as
>> > needed.  If no bodhi ticket is found, do not create a new one, just
>> > leave the build as is.  This work will begin soon.
>> >
> How does this strategy go for packages that the latest dist-f14 one
> was rebuilt using gcc-4.5.1-3.fc14, and there is newer dist-f14-updates-candidate
> one rebuilt using gcc-4.5.1-3.fc14 but no bodhi submission yet?

Hrm.  I'll have to check for this specific scenario and tease out
anything which fits.  In these cases I think I'll have to look by hand
at what the differences are between the dist-f14 build and the
dist-f14-updates-candidate build is, and then work with the maintainer
on whether an update should be pushed or a build with the only change
being the gcc update done and pushed instead.

- -- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyrsn8ACgkQ4v2HLvE71NVhlACfUyXs6f2tP00/cwc6rZkyyaSB
F/gAnRHUZ46X9gBDODfTBDCCp+8kcMcs
=ffJI
-----END PGP SIGNATURE-----