Re: Bug in update_excuses?

[Andreas Metzler <ametzler@logic.univie.ac.at>]

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:
> 
> 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)
> 
> Valid candidates can also be held up for other reasons - for example,
> because they would break other things.

Ok. I reformulate: db3 should show _some_ sign in updates_excuses
about not being upgraded because it is invalidated by dependency.

I had wondered about why db3 suddenly started to show up as showstopper[1]
and the only way to actually find out why was to manually check the
dependencies of the binary NMU for s390.
              cu andreas

[1] I know it is not really a showstopper, because anything depending
on libdb3 will be stopped by its own dependency on glibc.