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

Bug#740375: marked as done (transition: poppler 0.24)

Your message dated Thu, 24 Apr 2014 19:53:08 +0200
with message-id <20140424175308.GC4433@betterave.cristau.org>
and subject line Re: Bug#740375: transition: poppler 0.24
has caused the Debian Bug report #740375,
regarding transition: poppler 0.24
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
740375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740375
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hi,

I would like to ask a slot for a Poppler 0.24.x transition.
I know a 0.22 transition has been done recently, but the future 0.26
will not be released at least for another month and it breaks few
sources using the private libpoppler, so I would like to introduce 0.24
in Debian soon.
Currently there is Poppler 0.24.x in experimental already.

This transition impacts the existing poppler libraries in the following ways:
- libpoppler37 → libpoppler44

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
  gdcm
  gnome-commander
  inkscape 
  pdf2djvu
  pdftoipe
  popplerkit.framework
  texlive-bin

Sources that currently FTBFS:

* xpdf
    The version currently in unstable does not support Poppler 0.24,
    while the version in experimental does (#736443).

* libreoffice
    LO 4.1 does not support Poppler 0.24 (needs an upstream commit [1]),
    while LO 4.2 (currently in experimental) does. Thus it is matter of
    either backporting that commit, or pushing LO 4.2 in unstable.

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.24

A ben tracker for poppler would have:
is_affected = .build-depends ~ "libpoppler-private-dev";
is_good = .depends ~ "libpoppler44";
is_bad = .depends ~ "libpoppler37";

[1] http://cgit.freedesktop.org/libreoffice/core/commit/?id=828ebc542b980fce90e70459eb2d13e6eeecc355

Thanks,
-- 
Pino

--- End Message ---
--- Begin Message --- 
On Fri, Feb 28, 2014 at 19:44:28 +0100, Pino Toscano wrote:

> I would like to ask a slot for a Poppler 0.24.x transition.
> I know a 0.22 transition has been done recently, but the future 0.26
> will not be released at least for another month and it breaks few
> sources using the private libpoppler, so I would like to introduce 0.24
> in Debian soon.
> Currently there is Poppler 0.24.x in experimental already.
> 
> This transition impacts the existing poppler libraries in the following ways:
> - libpoppler37 → libpoppler44
> 
All done I think.  Closing.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: