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

Bug#751525: transition: poppler 0.26



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

Sources that currently FTBFS:

* gdcm
    Compatibility with Poppler 0.26.x fixed upstream, asked to backport
    the patches in #751432.

Other cases:

* derivations
    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.

I grouped all the bugs mentioned above (even the solved ones) with the
following usertag:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pino@debian.org;tag=poppler-0.26

A ben tracker for poppler would have:
title = "poppler 0.26";
is_affected = .build-depends ~ "libpoppler-private-dev" | .source ~ /texworks/;
is_good = .depends ~ "libpoppler46";
is_bad = .depends ~ "libpoppler44";

Thanks,
-- 
Pino


Reply to: