On 2012-02-24 09:33, Ansgar Burchardt wrote: > Niels Thykier <ni...@thykier.net> writes: >> [...] >> Assuming there will be a source package in Sources only kept due to >> Built-Using, then Britney may (or may not) keep its counterpart in >> testing until the source package disappears from Sources (in sid). If >> it does not have any binaries and it is not in testing, then she will at >> least keep it out of testing[2]. > > dak would also include them in Sources for testing, britney could not > remove them as they are handled differently in dak. Would britney > handle that as well? >
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 I suspect 2 might happen if we remove something from testing. Though the sid version probably won't migrate then. To me, it looks like they will be "reduced to a previously known solution". Adam, can you see another case for the "reappearing" sources? > For reference here are the sources that would currently be included in > Sources right now: > > [...] > > Regards, > Ansgar > > > ~Niels -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org