Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
Control: block -1 by 679896 719224 712688
Hi,
I would like to ask a slot for a Poppler 0.22.x transition.
Currently there is Poppler 0.22.x in experimental already. Please note
that there are still few issues that prevents it to be started,
so I'm filing this at this time to have this transition considered
by the release team.
This transition impacts the existing poppler libraries in the following ways:
- libpoppler19 → libpoppler37
- libpoppler-glib8 -- BC with 0.18;
provides symbols file (with few new symbols though)
- libpoppler-qt4-3 → libpoppler-qt4-4
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 (poppler, poppler-qt4)
comparepdf (poppler-qt4)
cups-filters (poppler)
diffpdf (poppler-qt4)
gambas3 (poppler)
gdcm (poppler)
gnome-commander (poppler)
inkscape (poppler)
katarakt (poppler-qt4)
kbibtex (poppler-qt4)
ktikz (poppler-qt4)
libreoffice (poppler)
luatex (poppler)
nepomuk-core (poppler-qt4)
okular (poppler-qt4)
pdf2djvu (poppler)
pdftoipe (poppler)
popplerkit.framework (poppler)
prerex (poppler-qt4)
python-poppler-qt4 (poppler-qt4)
qcomicbook (poppler-qt4)
qpdfview (poppler-qt4)
tellico (poppler-qt4)
texlive-bin (poppler)
texmaker (poppler-qt4)
texstudio (poppler-qt4)
texworks (poppler-qt4)
Sources that currently FTBFS:
* gdal (poppler)
gdal currently in unstable FTBFS with new Poppler (#679887), while
the version in experimental builds fine.
OTOH, gdal/experimental needs a transition (#712688).
* xpdf (poppler)
The patches needed to compile with poppler 0.22.x are not compatible
with poppler 0.18, so they cannot be uploaded to unstable right now.
They are #679896 (for 0.18 → 0.20) and #719224 (for 0.20 → 0.22).
Other cases:
* derivations (poppler)
This source builds a libpoppler-based utility application which is
only used during the build to generate other data, and no trace of
that application are left in the resulting arch:all package.
It currently FTBFS with Poppler >= 0.20 (#690161), but given what
said above it can be left out of the transition (the bug severity
will be raised to "serious" once the transition starts).
I grouped all the bugs mentioned above (even the solved ones) with the
following usertag:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=p...@debian.org;tag=poppler-0.20
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=p...@debian.org;tag=poppler-0.22
A ben tracker for poppler would have:
title = "poppler 0.22";
is_affected = .build-depends ~ "libpoppler-private-dev" | .build-depends ~
"libpoppler-qt4-dev";
is_good = .depends ~ "libpoppler37" | .depends ~ "libpoppler-qt4-4";
is_bad = .depends ~ "libpoppler19" | .depends ~ "libpoppler-qt4-3";
Thanks,
--
Pino
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130809134519.6839.93451.reportbug@drak
