Outdated binaries in the archive due to Packages-arch-specific or FTBFS

Max Bowsher maxb at f2s.com
Mon Dec 29 16:06:24 UTC 2008


There are quite a number of outdated binaries in the archive in
universe, which is not covered by the current britney outdate report. A
significant portion of these are outdate because Packages-arch-specific
masks them preventing any new builds, but the old binaries have not been
removed from the archive.

I've made a list of all packages which were outdate in intrepid and are
still outdate in jaunty, and now want to start filing bugs against them
- what should I do in these bugs: Subscribe ubuntu-archive for NBS
processing, or leave them for a MOTU/core-dev to ack the need for NBS
removal?

If the second, is there some way the bugs should be tagged as relating
to archive cleanliness, so they can be usefully queried for?


The outdates which are not due to Packages-arch-specific are generally
FTBFS bugs - there are even some packages which have been FTBFS since
hoary (!).  When a package has been FTBFS for a long time, is there some
way to mark the FTBFS bug such that the outdated binaries will get
removed before Jaunty is released, if no one has got around to fixing them?


Max.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20081229/678e6e1d/attachment.pgp>


More information about the Ubuntu-devel-discuss mailing list