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

Bug#511762: marked as done (hpijs-ppds: Several ppds not working with newer cups)

Your message dated Sun, 29 Oct 2017 13:08:24 +0000
with message-id <29102017125910.f258e56ce698@desktop.copernicus.org.uk>
and subject line Re: Bug#511762: hpijs-ppds: Several ppds not working with newer cups
has caused the Debian Bug report #511762,
regarding hpijs-ppds: Several ppds not working with newer cups
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.)


-- 
511762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511762
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: hpijs-ppds
Version: 2.8.6.b-3
Severity: important

Due to the more strict interpreter in cups 1.3.8 I get the following error 
with /usr/share/ppd/hpijs/HP/HP_Color_LaserJet_2605-ps.ppd:

PPD file for Farblaser cannot be loaded!
Missing value string on line 122.
Hint: Run "cupstestppd /etc/cups/ppd/Farblaser.ppd" and fix any errors.

this is valid for 2.8.6.b-3 in Lenny and also for 2.8.12-1 in experimental.
(My printer URI in cups is: usb://HP/Color%20LaserJet%<sernum>.)

The ppds for this printer (HP_Color_LaserJet_2605.ppd) in
foomatic-db 20080211-2+nmu1 and
openprinting-ppds 20080211-2+nmu1
are correct. See also 
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493104> or
<http://bugs.linux-foundation.org/show_bug.cgi?id=164>

Maybe it is possible to run the cupstestppd and remove/fix failing ppds during 
the build process of the deb?

By the way, the actual file in experimental contains many duplicate files 
compressed, uncompressed, small/uppercase letters.


-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.27.10
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages hpijs-ppds depends on:
ii  foomatic-filters      3.0.2-20080211-3.2 OpenPrinting printer support -
ii  hpijs                 2.8.6.b-3          HP Linux Printing and Imaging -

hpijs-ppds recommends no packages.

Versions of packages hpijs-ppds suggests:
ii  hplip                         2.8.6.b-3  HP Linux Printing and Imaging

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Wed 14 Jan 2009 at 10:02:06 +0100, Thomas Viehweger wrote:

> Package: hpijs-ppds
> Version: 2.8.6.b-3
> Severity: important
> 
> Due to the more strict interpreter in cups 1.3.8 I get the following error 
> with /usr/share/ppd/hpijs/HP/HP_Color_LaserJet_2605-ps.ppd:
> 
> PPD file for Farblaser cannot be loaded!
> Missing value string on line 122.
> Hint: Run "cupstestppd /etc/cups/ppd/Farblaser.ppd" and fix any errors.
> 
> this is valid for 2.8.6.b-3 in Lenny and also for 2.8.12-1 in experimental.
> (My printer URI in cups is: usb://HP/Color%20LaserJet%<sernum>.)
> 
> The ppds for this printer (HP_Color_LaserJet_2605.ppd) in
> foomatic-db 20080211-2+nmu1 and
> openprinting-ppds 20080211-2+nmu1
> are correct. See also 
> <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493104> or
> <http://bugs.linux-foundation.org/show_bug.cgi?id=164>
> 
> Maybe it is possible to run the cupstestppd and remove/fix failing ppds during 
> the build process of the deb?
> 
> By the way, the actual file in experimental contains many duplicate files 
> compressed, uncompressed, small/uppercase letters.

This report is in the context of cups and hplip packages which are no
longer supported. Please submit a new report if the issue arises with
the packages in unstable (cups 2.2.5-2 and hplip 3.17.10+repack0-1, or
later versions).

Regards,

Brian.

--- End Message ---
Reply to: