Bug#751525: transition: poppler 0.26

2014-07-07 Thread Emilio Pozuelo Monfort
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.

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751525: transition: poppler 0.26

2014-07-07 Thread Pino Toscano

On 2014-07-07 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.


I can try, although not for the next couple of days, sorry :-/
Wouldn't be possible to smooth-migrate poppler anyway?

Oh, and it seems like poppler now is waiting for the qtbase
transition... (maybe a gb of gammaray could make it build again)

--
Pino Toscano


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751525: transition: poppler 0.26

2014-07-03 Thread Pino Toscano

On 2014-07-03 00:39, Emilio Pozuelo Monfort wrote:

On 13/06/14 20:41, Pino Toscano wrote:

Package: release.debian.org
Severity: normal
User: release.debian@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


Scheduled.


Thanks!

I would have pinged when having successful poppler builds everywhere,
but you where faster in scheduling binNMUs :)


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.

--
Pino Toscano


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751525: transition: poppler 0.26

2014-07-02 Thread Emilio Pozuelo Monfort
On 25/06/14 20:47, Pino Toscano wrote:
 Hi,
 
 On 2014-06-24 10:52, Emilio Pozuelo Monfort wrote:
 On 14/06/14 12:11, Emilio Pozuelo Monfort wrote:
 On 13/06/14 20:41, Pino Toscano wrote:
 Package: release.debian.org
 Severity: normal
 User: release.debian@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:

 Looks so good that I was going to ack it immediately, but unfortunately
 libreoffice clashes with the ongoing iceweasel transition, so let's wait 
 until
 that finishes.

 libreoffice is about to transition, so please go ahead. I'll just wait until
 libreoffice migrates before scheduling its binNMU.
 
 Thanks for the ACK.
 
 Unfortunately I'm not that available for uploading, NMU gdcm and
 following the transition in the next 7 days.
 Please let me know whether there are blockers before July 3rd.

There are none atm. Please go ahead when you get back.

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751525: transition: poppler 0.26

2014-07-02 Thread Emilio Pozuelo Monfort
Control: tags -1 pending

On 13/06/14 20:41, Pino Toscano wrote:
 Package: release.debian.org
 Severity: normal
 User: release.debian@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

Scheduled.

 Sources that currently FTBFS:
 
 * gdcm
 Compatibility with Poppler 0.26.x fixed upstream, asked to backport
 the patches in #751432.

That's RC now.

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751525: transition: poppler 0.26

2014-06-25 Thread Pino Toscano

Hi,

On 2014-06-24 10:52, Emilio Pozuelo Monfort wrote:

On 14/06/14 12:11, Emilio Pozuelo Monfort wrote:

On 13/06/14 20:41, Pino Toscano wrote:

Package: release.debian.org
Severity: normal
User: release.debian@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:


Looks so good that I was going to ack it immediately, but 
unfortunately
libreoffice clashes with the ongoing iceweasel transition, so let's 
wait until

that finishes.


libreoffice is about to transition, so please go ahead. I'll just 
wait until

libreoffice migrates before scheduling its binNMU.


Thanks for the ACK.

Unfortunately I'm not that available for uploading, NMU gdcm and
following the transition in the next 7 days.
Please let me know whether there are blockers before July 3rd.

Thanks,
--
Pino Toscano


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751525: transition: poppler 0.26

2014-06-24 Thread Emilio Pozuelo Monfort
Control: tags -1 confirmed

On 14/06/14 12:11, Emilio Pozuelo Monfort wrote:
 On 13/06/14 20:41, Pino Toscano wrote:
 Package: release.debian.org
 Severity: normal
 User: release.debian@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:
 
 Looks so good that I was going to ack it immediately, but unfortunately
 libreoffice clashes with the ongoing iceweasel transition, so let's wait until
 that finishes.

libreoffice is about to transition, so please go ahead. I'll just wait until
libreoffice migrates before scheduling its binNMU.

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751525: transition: poppler 0.26

2014-06-14 Thread Emilio Pozuelo Monfort
On 13/06/14 20:41, Pino Toscano wrote:
 Package: release.debian.org
 Severity: normal
 User: release.debian@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:

Looks so good that I was going to ack it immediately, but unfortunately
libreoffice clashes with the ongoing iceweasel transition, so let's wait until
that finishes.

Note that there are auto trackers, so there should be no need to provide ben
files in normal situations.

https://release.debian.org/transitions/html/auto-poppler.html

Regards,
Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#751525: transition: poppler 0.26

2014-06-13 Thread Pino Toscano
Package: release.debian.org
Severity: normal
User: release.debian@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=p...@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


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org