Bug#922484: nmu: paw_1:2.14.04.dfsg.2-9.1, mclibs_20061220+dfsg3-3.1, geant321_1:3.21.14.dfsg-11
Control: tags -1 + confirmed On Fri, 2019-02-22 at 10:08 +0100, Emilio Pozuelo Monfort wrote: > Control: tags -1 stretch > > On 21/02/2019 23:55, Andreas Beckmann wrote: > > On Sat, 16 Feb 2019 22:09:11 +0100 Gilles Filippini > g> wrote: > > > Now that #922453 is fixed, paw, mclibs and geant321 have to be > > > rebuilt > > > against this fixed cernlib release. [...] > > 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. I think a clone + close would have been cleaner, but never mind. Scheduled, with the correct version in the dep-waits (it's 4.3+, not 4.4~). Regards, Adam
Bug#922484: nmu: paw_1:2.14.04.dfsg.2-9.1, mclibs_20061220+dfsg3-3.1, geant321_1:3.21.14.dfsg-11
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 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. signature.asc Description: OpenPGP digital signature
Bug#922484: nmu: paw_1:2.14.04.dfsg.2-9.1, mclibs_20061220+dfsg3-3.1, geant321_1:3.21.14.dfsg-11
Control: tags -1 stretch On 21/02/2019 23:55, Andreas Beckmann wrote: > On Sat, 16 Feb 2019 22:09:11 +0100 Gilles Filippini 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). > > 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. Cheers, Emilio
Bug#922484: nmu: paw_1:2.14.04.dfsg.2-9.1, mclibs_20061220+dfsg3-3.1, geant321_1:3.21.14.dfsg-11
On Sat, 16 Feb 2019 22:09:11 +0100 Gilles Filippini 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). 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" 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) Andreas
Bug#922484: nmu: paw_1:2.14.04.dfsg.2-9.1, mclibs_20061220+dfsg3-3.1, geant321_1:3.21.14.dfsg-11
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Release team, Now that #922453 is fixed, paw, mclibs and geant321 have to be rebuilt against this fixed cernlib release. nmu paw_1:2.14.04.dfsg.2-9.1 . ANY . unstable . -m "rebuild against fixed cernlib regarding #922453" nmu mclibs_20061220+dfsg3-3.1 . ANY . unstable . -m "rebuild against fixed cernlib regarding #922453" nmu geant321_1:3.21.14.dfsg-11 . ANY . unstable . -m "rebuild against fixed cernlib regarding #922453" Thanks in advance; _g. - -- System Information: Debian Release: buster/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlxoe+wACgkQ7+hsbH/+ z4P8ywf+OdYQS2XYWdGZ9y5bBJoQGT0mQ0zvD+SdFfgAMU9o+91FqhTtxB8jTLd2 QQpkcBgaI+U/PIzKWVea3Tyu2sEzL5sm7J/GWKe5sYOYp3sQSftp+Sz0IRmoXhzA BHENzlB/L/vs00yJWrMH/h5/t2DH/s99K5dxYfV/V3fA9HbWWuvTmTteQ6ecsOP3 Xr09Vbhh3iuWR1x6yiyTvOETJer9CxyMX+SQSHai6wKYZNP8aKPoVP7QPl4I8goN B6B7clVuAhTTtDInfTN+0RxHgX2pIuxEoPDJGUxefhY2VJvLnUl/FCaRaneyZx3d /xsODhYvd5BIO2Hox3GS7jnDa6faeQ== =ZIna -END PGP SIGNATURE-
