The Developer and Games spin both fail to compose due to missing packages. They will not be shipped as part of Fedora 10 Preview, and run the risk of not being part of Fedora 10.
Jesse Keating wrote:
The Developer and Games spin both fail to compose due to missing packages. They will not be shipped as part of Fedora 10 Preview, and run the risk of not being part of Fedora 10.
Too bad... I'm trying to find ways to deal with this kind of situation:
1) Compose, compose, compose and see what the results are, which would need to be automated to prevent a maintainer requiring a random large number of resources.
2) Allow --ignore-missing to %packages, which would be a bad motivator to ignore
3) Have maintainers watch the rawhide change reports on whether relevant packages are nuked from the distribution, which in fact is what they should be doing already
4) Nuke the spins at the moment they appear to not be maintained properly which would seem like a form of punishment I'm not in favor of.
What say you all?
-Jeroen
On Wed, 2008-11-05 at 12:41 +0100, Jeroen van Meeuwen wrote:
- Compose, compose, compose and see what the results are, which would
need to be automated to prevent a maintainer requiring a random large number of resources.
Work is still in progress with this one, once we get out of the F10 crunch I hope to have a daily compose attempt going for all approved official "spins" for a release.
That in conjunction with spin owners paying attention to when we do freezes and scm branches, testing their configs at branch time is really really important.
And finally, two strikes your out. (but that gets harder to enforce very late in the dev cycle, but...)