libgdl-2.24.0: libgdl-gnome-1.so dropped

[Alex Lancaster]

>>>>> "KK" == Kevin Kofler  writes:

KK> Alex Lancaster <alexl <at> users.sourceforge.net> writes:
>> Can this be fixed as well?  Also, you might consider chain-build in
>> rawhide to rebuild a series of packages against each other so that
>> the rawhide push passes repoclosure and doesn't have any broken
>> deps, even transiently.  Otherwise you could also ask rel-eng for a
>> buildroot override.

KK> Buildroot overrides are not useful for Rawhide. They're what is
KK> used to build chains of dependent packages in releases. (You can't
KK> just chain-build them because updates-candidate doesn't populate
KK> the buildroots.)

KK> Basically, chain-building works if and only if sequential building
KK> (with enough waiting for the buildroot's "newRepo" task to
KK> complete) works without needing manual tagging. So you can
KK> chain-build in Rawhide, you have to request manual tagging and
KK> wait for rel-eng to act on it and then for the automatic newRepo
KK> to happen in releases.

OK, I guess that was what I was suggesting was a manual tagging (would
that be dist-f10-build?) rather than a "build root override" per se.
As for chain-build, thanks for the clarification, you would need to
already have a new gdl tagged for dist-f10-build before the new builds
would use that?

Alex