Bug#740375: transition: poppler 0.24
On Mon, Apr 7, 2014 at 17:49:15 +0200, Pino Toscano wrote: - gdcm cannot be built on s390x due to the ongoing (and un-ACKed...) mpich transition (#742821), so maybe that transition should be brought forward (luckly it affects mostly s390x and mips/mipsel) So I've rebuilt boost1.54 to be able to rebuild vtk to be able to rebuild gdcm. Not much luck there, vtk FTBFS. Cheers, Julien signature.asc Description: Digital signature
Bug#740375: transition: poppler 0.24
On Mon, Apr 7, 2014 at 17:49:15 +0200, Pino Toscano wrote: On 2014-04-06 18:57, Julien Cristau wrote: On Sat, Apr 5, 2014 at 23:16:25 +0200, Pino Toscano wrote: Uploaded few hours ago, and now built everywhere. Scheduled binnmus (except for gdal, want to get -5 in testing first). Thanks for the binNMUs (no problem delaying gdal's binNMUs). gdal scheduled now. A small update regarding the situation so far: - gambas3 seems to be FTBFSing (what a surprise...) due to something related to pgsql; can be kicked out of testing, in case - gdcm cannot be built on s390x due to the ongoing (and un-ACKed...) mpich transition (#742821), so maybe that transition should be brought forward (luckly it affects mostly s390x and mips/mipsel) I'll try to move that along... *sigh* - gnome-commander FTBFSes on armel/armhf; the new upstream release 1.4.1 fixes that FTBFS, and also switches the libpoppler usage to poppler-glib (which would make it out of this transition); I contacted Alessio about it, and he should upload it within few days OK. In the mean time calligra failed on mipsel. Cheers, Julien signature.asc Description: Digital signature
Bug#740375: transition: poppler 0.24
On 2014-04-06 18:57, Julien Cristau wrote: On Sat, Apr 5, 2014 at 23:16:25 +0200, Pino Toscano wrote: Uploaded few hours ago, and now built everywhere. Scheduled binnmus (except for gdal, want to get -5 in testing first). Thanks for the binNMUs (no problem delaying gdal's binNMUs). A small update regarding the situation so far: - gambas3 seems to be FTBFSing (what a surprise...) due to something related to pgsql; can be kicked out of testing, in case - gdcm cannot be built on s390x due to the ongoing (and un-ACKed...) mpich transition (#742821), so maybe that transition should be brought forward (luckly it affects mostly s390x and mips/mipsel) - gnome-commander FTBFSes on armel/armhf; the new upstream release 1.4.1 fixes that FTBFS, and also switches the libpoppler usage to poppler-glib (which would make it out of this transition); I contacted Alessio about it, and he should upload it within few days -- 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#740375: transition: poppler 0.24
On Sat, Apr 5, 2014 at 23:16:25 +0200, Pino Toscano wrote: Uploaded few hours ago, and now built everywhere. Scheduled binnmus (except for gdal, want to get -5 in testing first). Cheers, Julien signature.asc Description: Digital signature
Bug#740375: transition: poppler 0.24
Control: tag -1 confirmed On Fri, Feb 28, 2014 at 19:44:28 +0100, Pino Toscano wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, I would like to ask a slot for a Poppler 0.24.x transition. Feel free to upload to unstable. Cheers, Julien signature.asc Description: Digital signature
Bug#740375: transition: poppler 0.24
Control: tag -1 pending On 2014-04-05 15:54, Julien Cristau wrote: On Fri, Feb 28, 2014 at 19:44:28 +0100, Pino Toscano wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi, I would like to ask a slot for a Poppler 0.24.x transition. Feel free to upload to unstable. Thanks! Uploaded few hours ago, and now built everywhere. -- 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#740375: transition: poppler 0.24
On Fri, Feb 28, 2014 at 08:39:15PM +0100, Rene Engelhard wrote: Could you please check whether LO/sid builds fine with poppler 0.24? Will do. Builds and the sdext_pdfimport cppunit check passes. Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740375: transition: poppler 0.24
On 2014-03-01 16:48, Rene Engelhard wrote: On Fri, Feb 28, 2014 at 08:39:15PM +0100, Rene Engelhard wrote: Could you please check whether LO/sid builds fine with poppler 0.24? Will do. Builds and the sdext_pdfimport cppunit check passes. Thanks a lot! So, release-team, only xpdf would actually need a sourceful upload for this transition, and the other dozen sources could just need a binNMU. -- 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#740375: transition: poppler 0.24
Package: release.debian.org Severity: normal User: release.debian@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=p...@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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740375: transition: poppler 0.24
Hi, On Fri, Feb 28, 2014 at 07:44:28PM +0100, Pino Toscano wrote: * libreoffice LO 4.1 does not support Poppler 0.24 (needs an upstream commit [1]), sure? That mentioned commit *is* in 4.1.5 afaics? Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740375: transition: poppler 0.24
On 2014-02-28 20:00, Rene Engelhard wrote: Hi, On Fri, Feb 28, 2014 at 07:44:28PM +0100, Pino Toscano wrote: * libreoffice LO 4.1 does not support Poppler 0.24 (needs an upstream commit [1]), sure? That mentioned commit *is* in 4.1.5 afaics? I know earlier versions of 4.1 didn't support 0.24, and I didn't check lately if it has been backported. Could you please check whether LO/sid builds fine with poppler 0.24? 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#740375: transition: poppler 0.24
Hi, On Fri, Feb 28, 2014 at 08:23:52PM +0100, Pino Toscano wrote: On Fri, Feb 28, 2014 at 07:44:28PM +0100, Pino Toscano wrote: * libreoffice LO 4.1 does not support Poppler 0.24 (needs an upstream commit [1]), sure? That mentioned commit *is* in 4.1.5 afaics? I know earlier versions of 4.1 didn't support 0.24, and I didn't check lately if it has been backported. Looking at git [1] was backported in 4.1.1. Could you please check whether LO/sid builds fine with poppler 0.24? Will do. Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
