Emilio Pozuelo Monfort a écrit le 22/02/2019 à 10:08 :
> Control: tags -1 stretch
> 
> On 21/02/2019 23:55, Andreas Beckmann wrote:
>> On Sat, 16 Feb 2019 22:09:11 +0100 Gilles Filippini <p...@debian.org> wrote:
>>> Now that #922453 is fixed, paw, mclibs and geant321 have to be rebuilt
>>> against this fixed cernlib release.
>>
>> Please binNMU the packages with a "gap" in the binNMU version s.t. this 
>> bug can be fixed by binNMUing in stable, too. The stretch binNMUs need a 
>> fixed cernlib in stretch-pu first of course (no pu request filed, yet).

I've just filed #922987.

>> given that we have these binary versions currently in stretch and sid:
>>
>> paw                         | 1:2.14.04.dfsg.2-9.1    | stable     | source, 
>> amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
>> paw                         | 1:2.14.04.dfsg.2-9.1+b2 | unstable   | amd64, 
>> arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
>>
>> libherwig59-2-dev           | 20061220+dfsg3-3.1      | stable     | amd64, 
>> armel, armhf, i386, mips, mipsel, s390x
>> libherwig59-2-dev           | 20061220+dfsg3-3.1+b2   | unstable   | amd64, 
>> armel, armhf, i386, mips, mipsel, s390x
>>
>> libgeant321-2-dev           | 1:3.21.14.dfsg-11+b2    | stable     | amd64, 
>> arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
>> libgeant321-2-dev           | 1:3.21.14.dfsg-11+b4    | unstable   | amd64, 
>> arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
>>
>> the following binNMUs should leave the required gap:
>>
>> nmu 4 paw_1:2.14.04.dfsg.2-9.1 . ANY . unstable . -m "rebuild against fixed 
>> cernlib regarding #922453"
>> nmu 4 mclibs_20061220+dfsg3-3.1 . ANY . unstable . -m "rebuild against fixed 
>> cernlib regarding #922453"
>> nmu 6 geant321_1:3.21.14.dfsg-11 . ANY . unstable . -m "rebuild against 
>> fixed cernlib regarding #922453"
> 
> Scheduled.
> 
>> For future reference, the corresponding binNMUs for stretch would be:
>>
>> nmu 3 paw_1:2.14.04.dfsg.2-9.1 . ANY . stretch . -m "rebuild against fixed 
>> cernlib regarding #922453"
>> dw paw_1:2.14.04.dfsg.2-9.1 . ANY . stretch . -m "cernlib-base-dev (>= 
>> 20061220+dfsg3-4.4~deb9u1)
>> nmu 3 mclibs_20061220+dfsg3-3.1 . ANY . stretch . -m "rebuild against fixed 
>> cernlib regarding #922453"
>> dw mclibs_20061220+dfsg3-3.1 . ANY . stretch . -m "cernlib-base-dev (>= 
>> 20061220+dfsg3-4.4~deb9u1)
>> nmu 5 geant321_1:3.21.14.dfsg-11 . ANY . stretch . -m "rebuild against fixed 
>> cernlib regarding #922453"
>> dw geant321_1:3.21.14.dfsg-11 . ANY . stretch . -m "cernlib-base-dev (>= 
>> 20061220+dfsg3-4.4~deb9u1)
> 
> I'll leave those to a SRM. I'm keeping this bug open and tagging it as stretch
> so the bug appears on their radar.

Thanks,

_g.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to