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

Bug#751525: marked as done (transition: poppler 0.26)

Your message dated Tue, 15 Jul 2014 00:51:47 +0200
with message-id <53C45F03.5060603@debian.org>
and subject line Re: Bug#751525: transition: poppler 0.26
has caused the Debian Bug report #751525,
regarding transition: poppler 0.26
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.)


-- 
751525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751525
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
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

--- End Message ---
--- Begin Message --- 
On 07/07/14 10:13, Emilio Pozuelo Monfort wrote:
> On 04/07/14 00:12, Pino Toscano wrote:
>> On 2014-07-03 00:39, Emilio Pozuelo Monfort wrote:
>>> On 13/06/14 20:41, Pino Toscano wrote:
>>>> 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.
> 
> gdcm failed on kfreebsd. Can you take a look? That's the last thing preventing
> testing migration.

poppler migrated a while ago but the last rdeps just migrated now, allowing the
old package to be removed from testing. Closing here now.

Emilio

--- End Message ---
Reply to: