[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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 <pini@debian.or
> > 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


Reply to: