Bug#666126: transition: poppler 0.18
Alle sabato 30 giugno 2012, Julien Cristau ha scritto: > On Wed, Mar 28, 2012 at 23:52:45 +0200, Pino Toscano wrote: > > I would like to ask a slot for a Poppler 0.18.x transition. > > Currently there is Poppler 0.18.4 in experimental already. Please > > note that there are still few issues that prevents it to be > > started, so I'm filing this at this time to have this transition > > considered by release-team. > > > > This transition impacts the existing poppler libraries in the > > following ways: - libpoppler13 → libpoppler19 > > - libpoppler-glib6 → libpoppler-glib8 > > - libpoppler-qt4-3 -- BC with 0.16, but bumps shlibs > > AFAICT that's all done, closing. It looks so, the transition tracker can be removed too. Thanks again for your effort in this, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#666126: transition: poppler 0.18
On Thu, Jun 14, 2012 at 04:06:48PM +0200, Pino Toscano wrote: > Hi Ricardo! > > Alle giovedì 14 giugno 2012, Ricardo Mones ha scritto: > > Seems rebuild has triggered http://bugs.debian.org/677345 > > Should I wait until poppler 0.18 transition ends or should I upload > > the fix right now? > > poppler 0.18 migrated to testing, so you can go ahead in fixing that Alright, tracker was/is at 94%, so I thought it wasn't finished... > (and #677521 too, please? ;) ). Yep, saw that too :) thanks, -- Ricardo Mones ~ The three principal virtues of a programmer are Laziness, Impatience, and Hubris.man perl signature.asc Description: Digital signature
Bug#666126: transition: poppler 0.18
Hi Ricardo! Alle giovedì 14 giugno 2012, Ricardo Mones ha scritto: > Seems rebuild has triggered http://bugs.debian.org/677345 > Should I wait until poppler 0.18 transition ends or should I upload > the fix right now? poppler 0.18 migrated to testing, so you can go ahead in fixing that (and #677521 too, please? ;) ). Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#666126: transition: poppler 0.18
On Mon, Jun 04, 2012 at 12:21:28AM +0200, Cyril Brulebois wrote: [...] > Did that on all archictectures: > > kibi@grieg:~$ wb nmu apvlv calibre cups-filters epdfview gdcm gimp > gle-graphics gnome-commander gpdftext gummi inkscape libextractor > pdf-presenter-console pdf2djvu pdf2svg pdfcube pdftoipe python-poppler > referencer tracker tumbler webkit2pdf xournal xpdf zathura . ALL . -m > 'Rebuild for the poppler transition.' Seems rebuild has triggered http://bugs.debian.org/677345 Should I wait until poppler 0.18 transition ends or should I upload the fix right now? regards, -- Ricardo Mones ~ The three principal virtues of a programmer are Laziness, Impatience, and Hubris.man perl signature.asc Description: Digital signature
Bug#666126: transition: poppler 0.18
Hello Pino, Pino Toscano (07/06/2012): > Apparently the way things based on poppler-sharp build makes them carry > a dependency on libpoppler-glib, so could you please > a) add "b-d on libpoppler-cil-dev" to the "affected" packages in the >transition tracker done. > b) binNMU pdfmod (the only source added by the above), which does >compile fine (just tested) Nope, arch:all package. Mraw, KiBi. signature.asc Description: Digital signature
Bug#666126: transition: poppler 0.18
Hi, Alle mercoledì 28 marzo 2012, Pino Toscano ha scritto: > A tracker for poppler would have > - "affected" packages: b-d on libpoppler-dev or > libpoppler-private-dev or libpoppler-glib-dev or libpoppler-qt4-dev > - "bad" packages: depends on libpoppler13 or libpoppler-glib6 - > "good" packages: depends on libpoppler19 or libpoppler-glib8 Apparently the way things based on poppler-sharp build makes them carry a dependency on libpoppler-glib, so could you please a) add "b-d on libpoppler-cil-dev" to the "affected" packages in the transition tracker b) binNMU pdfmod (the only source added by the above), which does compile fine (just tested) Sorry for having forgotten that detail, and thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#666126: transition: poppler 0.18
On Tue, Jun 5, 2012 at 17:12:29 +0100, Adam D. Barratt wrote: > On Mon, 2012-06-04 at 00:21 +0200, Cyril Brulebois wrote: > > kibi@grieg:~$ wb nmu apvlv calibre cups-filters epdfview gdcm gimp > > gle-graphics gnome-commander gpdftext gummi inkscape libextractor > > pdf-presenter-console pdf2djvu pdf2svg pdfcube pdftoipe python-poppler > > referencer tracker tumbler webkit2pdf xournal xpdf zathura . ALL . -m > > 'Rebuild for the poppler transition.' > > Was ruby-gnome2 intentionally not included, or simply overlooked? (I > didn't spot anything about it in the previous messages.) > I've scheduled it now, along with the missing 2 archs for popplerkit.framework. Cheers, Julien -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120605193209.gi31...@radis.cristau.org
Bug#666126: transition: poppler 0.18
On Mon, 2012-06-04 at 00:21 +0200, Cyril Brulebois wrote: > kibi@grieg:~$ wb nmu apvlv calibre cups-filters epdfview gdcm gimp > gle-graphics gnome-commander gpdftext gummi inkscape libextractor > pdf-presenter-console pdf2djvu pdf2svg pdfcube pdftoipe python-poppler > referencer tracker tumbler webkit2pdf xournal xpdf zathura . ALL . -m > 'Rebuild for the poppler transition.' Was ruby-gnome2 intentionally not included, or simply overlooked? (I didn't spot anything about it in the previous messages.) Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1338912749.3841.40.ca...@jacala.jungle.funky-badger.org
Bug#666126: transition: poppler 0.18
Julien Cristau (05/06/2012): > Having a version number in the changelog would be nice, ie poppler 0.18 > or libpoppler19. Ack. > Why the restriction on popplerkit.framework? Erm. Probably misread the table or pasted the wrong package name. Mraw, KiBi. signature.asc Description: Digital signature
Bug#666126: transition: poppler 0.18
On Mon, Jun 4, 2012 at 00:21:28 +0200, Cyril Brulebois wrote: > Pino Toscano (02/06/2012): > > I guess you could also exclude gambas3 and luatex for few days (to let > > the, migrate to testing first), and calligra (will get an upload of a > > new upstream release soon, and would be a waste to rebuild). > > Did that on all archictectures: > > kibi@grieg:~$ wb nmu apvlv calibre cups-filters epdfview gdcm gimp > gle-graphics gnome-commander gpdftext gummi inkscape libextractor > pdf-presenter-console pdf2djvu pdf2svg pdfcube pdftoipe python-poppler > referencer tracker tumbler webkit2pdf xournal xpdf zathura . ALL . -m > 'Rebuild for the poppler transition.' > Having a version number in the changelog would be nice, ie poppler 0.18 or libpoppler19. > > kibi@grieg:~$ wb nmu texlive-bin . ALL -sparc . -m 'Rebuild for the poppler > transition.' && wb nmu popplerkit.framework . ALL -amd64 -ia64 . -m 'Rebuild > for the poppler transition.' Why the restriction on popplerkit.framework? Now scheduled gambas3, luatex and evince. Cheers, Julien -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120605082504.ge31...@radis.cristau.org
Bug#666126: transition: poppler 0.18
Hello Pino, Pino Toscano (02/06/2012): > Thanks, I've uploaded poppler 0.18.4 to unstable yesterday, and it > compiled fine everywhere. thanks. > I've pinged this morning Chow Loong Jin, and later he kindly uploaded > the arch:all poppler-sharp. ACK. > I guess you could also exclude gambas3 and luatex for few days (to let > the, migrate to testing first), and calligra (will get an upload of a > new upstream release soon, and would be a waste to rebuild). Did that on all archictectures: kibi@grieg:~$ wb nmu apvlv calibre cups-filters epdfview gdcm gimp gle-graphics gnome-commander gpdftext gummi inkscape libextractor pdf-presenter-console pdf2djvu pdf2svg pdfcube pdftoipe python-poppler referencer tracker tumbler webkit2pdf xournal xpdf zathura . ALL . -m 'Rebuild for the poppler transition.' Arch-specific: kibi@grieg:~$ wb nmu texlive-bin . ALL -sparc . -m 'Rebuild for the poppler transition.' && wb nmu popplerkit.framework . ALL -amd64 -ia64 . -m 'Rebuild for the poppler transition.' Others: - didn't do gambas3 for now, - calligra, luatex are in level 2 anyway. (the former has been uploaded now, too) Hopefully I didn't forget too much… Mraw, KiBi. signature.asc Description: Digital signature
Bug#666126: transition: poppler 0.18
Hi, Alle giovedì 31 maggio 2012, Cyril Brulebois ha scritto: > Pino Toscano (30/04/2012): > > AFAICS, now the current block for this transition is the kpathsea > > transiton; also, there are other transitions which would conflict > > with this (openjpeg, exiv2, gdal, db5.3, ffi). > > I think we're good to go now, please upload. Thanks, I've uploaded poppler 0.18.4 to unstable yesterday, and it compiled fine everywhere. I've pinged this morning Chow Loong Jin, and later he kindly uploaded the arch:all poppler-sharp. > Rene asked for our waiting for libreoffice to migrate before we > schedule binNMUs, but that might not be going to happen right now > because of various problems with o-o-d binaries. So excluding libreoffice for now, could you please start scheduling the rebuilds? I guess you could also exclude gambas3 and luatex for few days (to let the, migrate to testing first), and calligra (will get an upload of a new upstream release soon, and would be a waste to rebuild). Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#666126: transition: poppler 0.18
Hi, On Thu, May 31, 2012 at 02:10:13PM +0200, Cyril Brulebois wrote: > Rene asked for our waiting for libreoffice to migrate before we schedule > binNMUs, but that might not be going to happen right now because of > various problems with o-o-d binaries. Which will be auto-cruft removed (when I get around uploading fixed transitional packages tonight). So it's just 2 days waiting time (assuming it gets auto-crufted fast). And a poppler upload to sid will need to wait a few days anyway so you can bin-NMU (or I do a source upload) then anyway... bin-NMUing now would again hinder LO 3.5.x migrating to testing replacing the rc-buggy/hosed up 3.4.x there (and testing has already stuff not working with 3.4.x).. Regards, Rene -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120531131054.ge25...@rene-engelhard.de
Processed: Re: Bug#666126: transition: poppler 0.18
Processing commands for cont...@bugs.debian.org: > tag 666126 pending Bug #666126 [release.debian.org] transition: poppler 0.18 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 666126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.133846939612310.transcr...@bugs.debian.org
Bug#666126: transition: poppler 0.18
tag 666126 pending thanks Pino Toscano (30/04/2012): > AFAICS, now the current block for this transition is the kpathsea > transiton; also, there are other transitions which would conflict with > this (openjpeg, exiv2, gdal, db5.3, ffi). I think we're good to go now, please upload. Rene asked for our waiting for libreoffice to migrate before we schedule binNMUs, but that might not be going to happen right now because of various problems with o-o-d binaries. Mraw, KiBi. signature.asc Description: Digital signature
Bug#666126: transition: poppler 0.18
Hi, Alle mercoledì 28 marzo 2012, Pino Toscano ha scritto: > I would like to ask a slot for a Poppler 0.18.x transition. An update on the status of this transition follows: > Sources that currently FTBFS: > > * gambas2 (poppler) > In a private talk with the gambas2 maintainer, he told me gambas2 > is not fit for wheezy and it will be replaced ASAP with gambas3. > No timing yet, though. > The gambas2 FTBFS has been reported as #651386. This is still unfixed, and it is RC-buggy for few months now. It seems there's no dependency issue in removing gambas2 from testing, so in case it could be hinted out of testing at transition time. > * luatex (poppler) > This is #651169. This has been fixed. > * poppler-sharp (poppler-glib) > This is an arch:all package, so it needs a sourceful upload. > It is #651385 and set as pending since some time. This is fixed in experimental (but will still need a sourceful "upload to unstable"), and I will ping Chow Loong Jin when the transition starts. > * pdfshuffler (python-poppler) > Due to the API loss in poppler-glib (the ones that require a > patch in python-poppler, see above) it will not run with a > python-poppler patched as in #651388. > It has been reported as #660937, and it is fixed upstream (with > maintainer waiting for an upstream release). The new version fixing the issue has been uploaded yesterday to unstable. > * python-poppler (poppler-glib) > The (small) patch needed to compile with poppler 0.18 breaks > compatibility with python apps using the few poppler-glib > functions dropped in poppler 0.16, so it cannot be uploaded right > now. Bug is #651388, and it will need a sourceful upload. Given that pdfshuffler has been fixed, the patch for python-poppler removing functions of poppler-glib dropped in 0.18 has been uploaded to unstable (after experimental) few hours ago. AFAICS, now the current block for this transition is the kpathsea transiton; also, there are other transitions which would conflict with this (openjpeg, exiv2, gdal, db5.3, ffi). -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#666126: transition: poppler 0.18
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.18.x transition. Currently there is Poppler 0.18.4 in experimental already. Please note that there are still few issues that prevents it to be started, so I'm filing this at this time to have this transition considered by release-team. This transition impacts the existing poppler libraries in the following ways: - libpoppler13 → libpoppler19 - libpoppler-glib6 → libpoppler-glib8 - libpoppler-qt4-3 -- BC with 0.16, but bumps shlibs 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: apvlv (poppler-glib) auto-multiple-choice (poppler) calibre (poppler) cups-filters (poppler) epdfview (poppler-glib) evince (poppler-glib) gdcm (poppler) gimp (poppler-glib) gnome-commander (poppler) gpdftext (poppler-glib) gummi (poppler-glib) inkscape (poppler, poppler-glib) koffice (poppler) libreoffice (poppler) openscenegraph (poppler-glib) pdf-presenter-console (poppler-glib) pdf2djvu (poppler) pdf2svg (poppler-glib) pdfcube (poppler-glib) pdfgrep (poppler) pdftoipe (poppler) popplerkit.framework (poppler) referencer (poppler-glib) ruby-gnome2 (poppler-glib) texlive-bin (poppler) tracker (poppler-glib) tumbler (poppler-glib) webkit2pdf (poppler-glib) xournal (poppler-glib) xpdf (poppler) zathura (poppler-glib) Sources that currently FTBFS: * gambas2 (poppler) In a private talk with the gambas2 maintainer, he told me gambas2 is not fit for wheezy and it will be replaced ASAP with gambas3. No timing yet, though. The gambas2 FTBFS has been reported as #651386. * luatex (poppler) This is #651169. * poppler-sharp (poppler-glib) This is an arch:all package, so it needs a sourceful upload. It is #651385 and set as pending since some time. * python-poppler (poppler-glib) The (small) patch needed to compile with poppler 0.18 breaks compatibility with python apps using the few poppler-glib functions dropped in poppler 0.16, so it cannot be uploaded right now. Bug is #651388, and it will need a sourceful upload. Other cases: * derivations (poppler) 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. This source can be left out of the transition (and it compiles fine with poppler 0.18 anyway). * pdfshuffler (python-poppler) Due to the API loss in poppler-glib (the ones that require a patch in python-poppler, see above) it will not run with a python-poppler patched as in #651388. It has been reported as #660937, and it is fixed upstream (with maintainer waiting for an upstream release). 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.18 A tracker for poppler would have - "affected" packages: b-d on libpoppler-dev or libpoppler-private-dev or libpoppler-glib-dev or libpoppler-qt4-dev - "bad" packages: depends on libpoppler13 or libpoppler-glib6 - "good" packages: depends on libpoppler19 or libpoppler-glib8 but since you already created it on my request, thanks! Thanks, -- Pino -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120328215245.25483.39058.reportbug@localhost.localdomain
