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

Bug#823667: marked as done (transition: poppler 0.44)

Your message dated Tue, 14 Jun 2016 19:39:23 +0200
with message-id <4b8a85ff-b9a5-d348-01af-ac5a7cf07cbe@debian.org>
and subject line Re: Bug#823667: transition: poppler 0.42
has caused the Debian Bug report #823667,
regarding transition: poppler 0.44
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.)


-- 
823667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823667
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.42.0 transition.
Currently there is Poppler 0.42.0 in experimental already.

This transition impacts the existing poppler libraries in the following ways:
- libpoppler57 → libpoppler60

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:

  boomaga
  cups-filters
  gambas3
  gdal
  gdcm
  inkscape
  ipe-tools
  libreoffice
  pdf2djvu
  pdf2htmlex
  popplerkit.framework
  texlive-bin
  texworks
  xpdf

Sources that currently FTBFS:

* calligra
    FTBFS for other reasons, not in testing already (can be ignored)

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.

A change in poppler-glib 0.39 is the removal of an unused enum; this so
far impacted only two sources:
  - ruby-gnome2 (#812677, fixed)
  - python-poppler (#812680)
OTOH, this issue does not directly affect the libpoppler transition.

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

Ben file:

title = "poppler 0.42";
is_affected = .depends ~ "libpoppler57" | .depends ~ "libpoppler60";
is_good = .depends ~ "libpoppler60";
is_bad = .depends ~ "libpoppler57";

Thanks,
-- 
Pino

--- End Message ---
--- Begin Message --- 
On 27/05/16 12:25, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
> 
> On 10/05/16 14:06, Emilio Pozuelo Monfort wrote:
>> On 07/05/16 13:34, Pino Toscano wrote:
>>> 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.42.0 transition.
>>> Currently there is Poppler 0.42.0 in experimental already.
>>>
>>> This transition impacts the existing poppler libraries in the following ways:
>>> - libpoppler57 → libpoppler60
>>>
>>> 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:
>>>
>>>   boomaga
>>>   cups-filters
>>>   gambas3
>>>   gdal
>>>   gdcm
>>>   inkscape
>>>   ipe-tools
>>>   libreoffice
>>>   pdf2djvu
>>>   pdf2htmlex
>>>   popplerkit.framework
>>>   texlive-bin
>>>   texworks
>>>   xpdf
>>>
>>> Sources that currently FTBFS:
>>>
>>> * calligra
>>>     FTBFS for other reasons, not in testing already (can be ignored)
>>>
>>> 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.
>>>
>>> A change in poppler-glib 0.39 is the removal of an unused enum; this so
>>> far impacted only two sources:
>>>   - ruby-gnome2 (#812677, fixed)
>>>   - python-poppler (#812680)
>>> OTOH, this issue does not directly affect the libpoppler transition.
>>>
>>> I grouped all the bugs mentioned above (even the solved ones) with the
>>> following usertag:
>>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pino@debian.org;tag=poppler-0.39
>>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pino@debian.org;tag=poppler-0.40
>>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pino@debian.org;tag=poppler-0.42
>>
>> Let's wait for a few days until the upcoming gdal upload migrates to testing.
> 
> Assuming there are no significant build regressions with the new version, you
> can go ahead.

I removed the last rdep in testing. This is done now.

Cheers,
Emilio

--- End Message ---
Reply to: