Jay Berkenbilt wrote:
>> I have been able to reproduce the problem locally. It doesn't look like
>> the result of an ABI change. I have yet to determine for sure whether
>> the problem is in libqpdf or whether it's in pdftopdf, but I'm assuming
>> libqpdf until I prove otherwise. I will refrai
Control: affects -1 cups-filters
Le mercredi, 10 juillet 2013 16.57:52, Jay Berkenbilt a écrit :
> Well, it does look like it must be an ABI change, though I can't yet
> figure out how as I'm looking very carefully at the bad commit and
> don't see anything that should constitute an ABI change. H
Jay Berkenbilt wrote:
>>> That might be, but if that's the case, that's of the responsibility of
>>> the libqpdf maintainer; if the ABI changed, it's a transition and
>>> binNMUs should have been requested.
>>>
>>> Cheers,
>>>
>>> OdyX
>>
>> I'm very alarmed as there were not supposed to be any
Jay Berkenbilt wrote:
> "Didier 'OdyX' Raboud" wrote:
>
>> Le mercredi, 10 juillet 2013 10.03:23, Till Kamppeter a écrit :
>>> Could perhaps a no-change rebuild of cups-filters help?
>>
>> That might be, but if that's the case, that's of the responsibility of
>> the libqpdf maintainer; if the A
"Didier 'OdyX' Raboud" wrote:
> Le mercredi, 10 juillet 2013 10.03:23, Till Kamppeter a écrit :
>> Could perhaps a no-change rebuild of cups-filters help?
>
> That might be, but if that's the case, that's of the responsibility of
> the libqpdf maintainer; if the ABI changed, it's a transition an
Le mercredi, 10 juillet 2013 10.03:23, Till Kamppeter a écrit :
> Could perhaps a no-change rebuild of cups-filters help?
That might be, but if that's the case, that's of the responsibility of
the libqpdf maintainer; if the ABI changed, it's a transition and
binNMUs should have been requested.
Could perhaps a no-change rebuild of cups-filters help?
Till
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Control: reassign -1 libqpdf10 4.1.0-2
Le mercredi, 10 juillet 2013 08.09:46, Johannes Stezenbach a écrit :
> On Wed, Jul 10, 2013 at 12:08:11AM +0100, Brian Potkin wrote:
> > On Tue 09 Jul 2013 at 20:43:09 +0100, Brian Potkin wrote:
> > > snapshot.debian.org has the previous versions of libqpdf10
On Wed, Jul 10, 2013 at 12:08:11AM +0100, Brian Potkin wrote:
> On Tue 09 Jul 2013 at 20:43:09 +0100, Brian Potkin wrote:
>
> > snapshot.debian.org has the previous versions of libqpdf10 and qpdf. So
> > I installed them (i386). Printing now takes place. Whether the bug lies
> > with one of those
On Tue 09 Jul 2013 at 20:43:09 +0100, Brian Potkin wrote:
> snapshot.debian.org has the previous versions of libqpdf10 and qpdf. So
> I installed them (i386). Printing now takes place. Whether the bug lies
> with one of those packages or not, I do not know. I suppose pdftopdf
> could still be at f
On Tue 09 Jul 2013 at 18:31:43 +0100, Brian Potkin wrote:
> Let's see what upgrading pulls in. A list of prospective packages is
> also attached.
>
> dist-upgrade. Print as before. But now we get the error 11. There is a
> log attached for that job too.
snapshot.debian.org has the previous versi
On Tue 09 Jul 2013 at 17:52:19 +0200, Johannes Stezenbach wrote:
> Did you get my other message where I said printing works
> after rebuilding the package locally? I'm not sure
> if it is worth it to track down which change in which
> library broke it. I don't print often so I can't tell
> when
On Tue, Jul 09, 2013 at 04:01:22PM +0100, Brian Potkin wrote:
> On Tue 09 Jul 2013 at 14:11:47 +0100, Brian Potkin wrote:
>
> > However, the Gutenprint and postscript driver both worked to produce
> > an expected output in /tmp. This is reason enough to question whether
>
> No they didn't! I real
severity 715448 grave
thanks
On Tue 09 Jul 2013 at 14:11:47 +0100, Brian Potkin wrote:
> However, the Gutenprint and postscript driver both worked to produce
> an expected output in /tmp. This is reason enough to question whether
No they didn't! I really should have checked the error log rathe
severity 715448 important
thanks
On Tue 09 Jul 2013 at 10:07:47 +0200, Johannes Stezenbach wrote:
Hello Johannes,
Thank you for the detail you have supplied.
> usually I'm using Kyocera FS-1020D Foomatic/hpijs-pcl5e via socket://,
> but the bug is reproducible with CUPS-PDF Printer both when
Package: cups-filters
Version: 1.0.34-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
usually I'm using Kyocera FS-1020D Foomatic/hpijs-pcl5e via socket://,
but the bug is reproducible with CUPS-PDF Printer both when
trying to print PDFs and using "Print Test Page" from
16 matches
Mail list logo
