Bug#625792: [britney2] Needs to be cleverer at deciding which packages to check for installability

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

On Fri, 2011-05-06 at 20:57 +0200, Julien Cristau wrote:
> On Fri, May  6, 2011 at 00:27:18 +0100, Adam D. Barratt wrote:
> 
> > thunar-vfs
> > - the source isn't in testing; so steps A, C and D are skipped
> > - unstable's ristretto doesn't depend on libthunar-vfs-1-2, so the
> > package isn't marked for checking again
> > 
> hrm, but why does unstable's ristretto matter at that point, rather than
> testing's?  (Apologies if I'm missing something obvious.)

It's not unstable's ristretto so much as unstable's thunar-vfs.

After adding thunar-vfs to testing, the record for the libthunar-vfs-1-2
binary built from that source is copied from unstable to testing,
including the previously computed list of reverse dependencies, which is
then used to look for affected packages.

I'm fairly sure one of my earlier debugging sessions included
re-scanning for affected packages after the reverse dependency list had
been updated, but it's not in my current version; I'll have another look
at that.

Regards,

Adam