tags 661078 confirmed thanks On 2012-02-24 10:03, Niels Thykier wrote: > On 2012-02-24 09:33, Ansgar Burchardt wrote: >> [...] > > I think so. If there are two sources with different version, she > completely ignores the lowest version. So that is definitely not a problem. > > Britney has her own copy of testing/Sources, which she maintains > (removing fields she doesn't care about etc.). So sources injected by > dak wouldn't be noticed unless we refresh those sources. I admit I do > not know if we do that regularly. > > That being said, the sources "(re)appearing" like this would (as far as > I can tell) basically fall into three cases: > 1 lower version than source of same name (in same suite) > => ignore/discard (see above) > 2 lower version in testing than source of same name in sid > => attempt to migrate sid version (as usual) > 3 source only in testing or (at end of run) source has no binaries in > testing > => attempt removal from testing > [...]
IRC chatting revealed at least one issue. Built-Using can make a "newer" source version appear in testing. """ build foo against bar 2. bar 1 is in testing. put foo in testing. """ The current suggestion is to use the Packages_X files to determine which source versions to use (and ignore the rest). Though: """ 09:21 < adsb> does it dtrt with smooth updates and/or faux packages? (not expecting an answer right now, just a thought) [...] 09:22 < adsb> it = "inferring Sources from Packages" """ As always, test cases are welcome at [1]. ~Niels [1] http://anonscm.debian.org/gitweb/?p=collab-maint/britney-tests.git -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org