On Mon, Sep 08, 2003 at 01:45:43PM +0100, Mark Brown wrote: > On Mon, Sep 08, 2003 at 02:07:23PM +0200, Andreas Metzler wrote: > > So the db3-update predepends on a glibc-update, which cannot happen and > > should stop db3 3.2.9-19.0.1 from becoming "Valid candidate", > > shouldn't it? > > The script considers if things are a valid candiate on their own merits > but assesses other things like dependencies separately - if look at > something like powertweak this is explicitly stated:
That's for when the dependency is a valid candidate, though. If it isn't then britney invalidates all the reverse dependencies, so you get things like the example you gave: > powertweak (0.99.4-19 to 0.99.5-1) > Maintainer: Mark Brown > 39 days old (needed 10 days) > Valid candidate > Invalidated by dependency > Not considered > Depends: powertweak glibc (not considered) The "Invalidated by dependency; Not considered" bit should have been output for db3/s390 too, but it wasn't. I think this is a bug in britney, although a minor one because db3/s390 will be thrown out at the next stage anyway due to increasing the uninstallability count. There's probably a glitch in the binary-NMU case. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]