On 07/15/2010 10:04 PM, Adam D. Barratt wrote: > Hi, > > On Thu, 2010-07-15 at 21:04 +0200, Thijs Kinkhorst wrote: >> We have run into a problem with libmikmod on stable-security in the most >> recent DSA. That was released with the version number 3.1.11-a-6+lenny1, >> following the usual scheme. However, as it seems hppa had a version that >> used >> the old binNMU numbering scheme: 3.1.11-a-6.0.1, which is considered newer: >> http://packages.debian.org/lenny/libmikmod2 > > [also visible on http://release.debian.org/proposed-updates/stable.html > fwiw] > >> Is there a way that we can solve this for hppa, or is the only way out a new >> DSA update for all 12 archs with only change a new version number? > > I've been trying to think of an answer that doesn't necessitate a > complete rebuild, but haven't come up with one thus far. > > Any solution that involves a sourceful upload will need to be rebuilt on > all architectures. I'm not sure if the security archive / buildd setup > makes it possible to only attempt to build a package on a restricted set > of architectures; even if it does, as soon as the package is accepted in > to proposed-updates the remaining architectures will then be auto-built > for stable.
I guess that only a manual build of a binNMU old scheme on hppa will save you from having a sourceful upload and rebuilds on all architectures. Probably the hppa buildd admins (in Cc) can help here? Cheers Luk -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c3f831c.70...@debian.org
