On 07/23/2013 09:03, Paul Wise wrote: > On Mon, Jul 22, 2013 at 10:14 PM, Cyril Brulebois wrote: >> I've just noticed that #699268 is supposed to be fixed, but last I heard >> about somebody from QA, that was during the last stages of the wheezy >> release cycle, and while the issue was known back then, I think not >> everyone agreed it was the right time to try and get that fixed (that >> conversation probably happened on #debian-release if memory serves, >> which I doubt). > > Hmm, ok. So you want madison to hide versions that exist but aren't > the latest version? The Debian archive has had the ability to have > multiple versions in the same suite for quite a while, I'm a bit > surprised this is coming up now. I seem to remember that Built-Using > isn't the only case where this can happen - library transitions can > too IIRC.
It's a matter of perspective. The archive software (dak) has a table that says which source package is in which suite (src_associations). This is what "dak ls" will show for which rmadison was an interface in the past. For a long time this was identical with what ended in the Sources indices, however dak now may include additional packages there. This is used to include source packages referenced by the (also new) Built-Using field which indicates additional source packages to keep as the full source of a binary package. This way they end up on all mirrors (including partial mirrors using debmirror) and CD images. These packages are marked with a "Extra-Source-Only: yes" header. See [1] and [2] for a bit more details. [1] <http://bugs.debian.org/657212> [2] <http://bugs.debian.org/661078> But with this there are now two different meanings for a source package being part of a suite: it can be in both src_associations and Sources OR it can be only in Sources. dak ls shows only the former group, rmadison shows both. I think that rmadison should behave like "dak ls" and only show source packages not marked as "Extra-Source-Only: yes". Please also not that the additional source packages included can be at a *higher* version than sources included in src_association. This is what happened here: grub2_1.99-27+deb7u1 is in jessie, however a package embedding a newer version of grub2 migrated to testing. This make grub2_2.00-14 appear in jessie's Sources as an additional source package. Ansgar -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ee48c7.7090...@debian.org
