182 pending F11 stable updates. WTF?

Michael Schwendt mschwendt at gmail.com
Mon May 11 20:27:29 UTC 2009


On Mon, 11 May 2009 21:31:31 +0200, Kevin wrote:

> Michael Schwendt wrote:
> 
> > On Mon, 11 May 2009 17:46:48 +0200, Ralf wrote:
> >  
> >> * Fact also is: "Testing" occasionally is the cause of broken package
> >> deps.
> > 
> > How? Or, what do you mean?
> 
> One example is Qt 4.5: it was in the buildroot, but only in testing, so
> stuff which got moved to stable before Qt 4.5 was was broken.

Can't parse that yet. :(

Builds pushed to updates-testing don't appear in the buildroots. They
need to be pushed to stable. Unless a buildroot override tag is used.

So, with the help of buildroot override you've had a complete set of Qt
4.5 builds in testing (as repoclosure has not detected related breakage),
but somebody pushed only parts of the builds to stable? (instead of
grouping all builds in a single bodhi ticket)

Then one cannot say "Testing [...] is the cause of broken package deps",
but once again, the improperly treated version upgrade has been the cause
of broken deps. For library ABI changes, it's "all or nothing". Either
push all related builds or none of them.




More information about the devel mailing list