On Sun, 2017-09-24 at 13:31 +0200, Aurelien Jarno wrote: > On 2017-09-24 10:41, Christoph Biedl wrote: [...] > > │ │ │ │ -libselinux (2.6-3+b2) sid; urgency=low, binary-only=yes > > │ │ │ │ +libselinux (2.6-3+b2) stretch; urgency=low, binary- > > only=yes > > │ │ │ │ > > │ │ │ │ * Binary-only non-maintainer upload for amd64; no source > > changes. > > │ │ │ │ - * Rebuild with python3.6 as a supported python3. > > │ │ │ │ + * Rebuild with current sbuild to fix changelog date > > │ │ │ │ > > │ │ │ │ - -- amd64 / i386 Build Daemon (x86-ubc-01) <buildd_amd64-x > > [email protected]> Thu, 29 Jun 2017 23:57:24 +0000 > > │ │ │ │ + -- amd64 / i386 Build Daemon (x86-ubc-01) <buildd_amd64-x > > [email protected]> Wed, 20 Sep 2017 03:33:46 +0000 > > > > Hmm I wonder what would have been the correct version for the binNMU > there. Using +b3 instead would have been forbidden as the version in > stretch needs to be lower than the version in buster/sid. >
In this particular case, testing and unstable have already moved onto 2.7-2, and the issue was simply that I hadn't spotted that the previous +b2 had existed in sid. Where there has been a version issue in the past, we've resorted to scheduling a binNMU with a higher revision in sid and then scheduling the stable binNMU in the "gap". Regards, Adam
