Re: Bug#1042057: binNMUs needed for new pandoc in *stable
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 makes sense
> > to fix it via (o)s-pu too.
> > ...
>
> In all 3 distributions this made libghc-{gitit,hakyll}-{dev,prof}
> uninstallable due to changed libghc-pandoc-{dev,prof}-* provides,
> e.g.:
> The following packages have unmet dependencies:
> libghc-gitit-dev : Depends: libghc-pandoc-dev-2.17.1.1-35d44
>
> For bullseye/bookworm this should be fixed with:
>
> wb nmu gitit . ANY . bookworm . -m 'Rebuild against new pandoc'
> wb nmu haskell-hakyll . ANY . bookworm . -m 'Rebuild against new
> pandoc'
>
> wb nmu gitit . ANY . bullseye . -m 'Rebuild against new pandoc'
> wb nmu haskell-hakyll . ANY . bullseye . -m 'Rebuild against new
> pandoc'
>
Both packages already have binNMUs, so need the binNMU number
specifying. Both already have binNMUs in stable and unstable that have
consecutive versions, so I've scheduled higher-versioned ones in
unstable to make some room:
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 gitit haskell-hakyll . ANY . bullseye . -m "Rebuild against new pandoc; see #1042057"
Regards,
Adam
Reply to: