On Thu, Jun 14, 2012 at 12:40 PM, Cyril Brulebois wrote: > Michael Gilbert <mgilb...@debian.org> (14/06/2012): >> package (version) sid; urgency=low >> >> * Binary-only non-maintainer upload; no source changes. >> >> -- Debian Release Team <debian-release@lists.debian.org> Tue, 05 Jun >> 2012 16:33:05 +0000 >> >> or some other appropriate binnmu mailing address. This would also >> mean rebuilding all of the other architectures for multi-arch same >> packages so that they all get the same changelog. > > No, binNMUs numbers can be different, along with timestamps (even with: > “wb nmu foo . ALL . -m 'Rebuild for foo.'”, architectures are processed > one after each other). Also, reasons can be different.
Right, I imagine it will involving reworking of quite a few steps in the process, and again this would be only for 'multi-arch: same'. So, instead of the buildd (or wherever that is done now) creating the changelog/timestamp, instead create one 'multi-arch: same' changelog before passing it off to the buildds, and then after the build is done, replace the automatically architecture-specific changelog with the 'multi-arch: same' one. The reason for rebuilding a 'multi-arch: same' package by definition should be for the same reason on all architectures, right? Non 'multi-arch: same' binnmus would not need to change. Best wishes, Mike -- 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/CANTw=mpnlz6gvczq2scfyzvzu_qvtn_s9ab7+i9kbjozled...@mail.gmail.com
