Bug#1042057: binNMUs needed for new pandoc in *stable

2023-10-02 Thread Adam D. Barratt
On Sun, 2023-10-01 at 22:33 +0100, Adam D. Barratt wrote: > On Sun, 2023-10-01 at 18:37 +0100, Adam D. Barratt wrote: > > wb nmu 10 gitit haskell-hakyll . ANY . unstable . -m "Rebuild to > > clear version space for rebuilds in stable; see #1042058" > > wb nmu 6 gitit haskell-hakyll . ANY .

Bug#1042057: binNMUs needed for new pandoc in *stable

2023-10-01 Thread Adam D. Barratt
On Sun, 2023-10-01 at 18:37 +0100, Adam D. Barratt wrote: > wb nmu 10 gitit haskell-hakyll . ANY . unstable . -m "Rebuild to > clear version space for rebuilds in stable; see #1042058" > wb nmu 6 gitit haskell-hakyll . ANY . bookworm . -m "Rebuild against > new pandoc; see #1042058" > wb nmu 2

Bug#1042057: binNMUs needed for new pandoc in *stable

2023-10-01 Thread Adam D. Barratt
On Sun, 2023-10-01 at 19:57 +0300, Adrian Bunk wrote: > On Tue, Jul 25, 2023 at 11:39:38PM +0200, Guilhem Moulin wrote: > > ... > > The Security Team decided not to issue a DSA for that CVE, but it's > > now fixed in > > buster-security (2.2.1-3+deb10u1) as well as sid (2.17.1.1-2), so > > it

Bug#1042057: binNMUs needed for new pandoc in *stable

2023-10-01 Thread Adrian Bunk
On Tue, Jul 25, 2023 at 11:39:38PM +0200, Guilhem Moulin wrote: >... > The Security Team decided not to issue a DSA for that CVE, but it's now fixed > in > buster-security (2.2.1-3+deb10u1) as well as sid (2.17.1.1-2), so it makes > sense > to fix it via (o)s-pu too. >... In all 3 distributions