Bug#751525: transition: poppler 0.26

[Pino Toscano <pino@debian.org>]

On 2014-07-03 00:39, Emilio Pozuelo Monfort wrote:
> On 13/06/14 20:41, Pino Toscano wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian.org@packages.debian.org
> > Usertags: transition
> > Control: block -1 by 751432
> >
> > Hi,
> >
> > I would like to ask a slot for a Poppler 0.26.x transition.
> > Currently there is Poppler 0.26.1 in experimental already.
> >
> > This transition impacts the existing poppler libraries in the 
> > following ways:
> > - libpoppler44 → libpoppler46
> > - libpoppler-glib8 -- BC with 0.24 (with few new symbols)
> > - libpoppler-qt4-4 -- BC with 0.24 (with one new symbol)
> > - libpoppler-qt5-1 -- BC with 0.24 (with one new symbol)
> >
> > Below it is a list of sources which are touched by the transition, 
> > and their
> > situation, sorted by solutions:
> >
> > Sources that compile fine, and can be binNMU'ed:
> >
> >   calligra
> >   cups-filters
> >   gambas3
> >   gdal
> >   inkscape
> >   libreoffice
> >   pdf2djvu
> >   pdftoipe
> >   popplerkit.framework
> >   texlive-bin
> >   texworks (has a spurious dependency on libpoppler, handling it
> >            upstream and then to Debian)
> >   xpdf
>
> Scheduled.

Thanks!

I would have pinged when having successful poppler builds everywhere,
but you where faster in scheduling binNMUs :)

> > Sources that currently FTBFS:
> >
> > * gdcm
> >     Compatibility with Poppler 0.26.x fixed upstream, asked to 
> > backport
> >     the patches in #751432.
>
> That's RC now.

... and NMU uploaded to DELAYED/2.

--
Pino Toscano