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

Bug#1008210: marked as done (cups-client: lp (-h) hostname option has to come before destination (-d))

Your message dated Sun, 14 Aug 2022 12:16:53 +0100
with message-id <14082022121321.6e736cafab10@desktop.copernicus.org.uk>
and subject line Re: Bug#1008210: cups-client: lp (-h) hostname option has to come before destination (-d)
has caused the Debian Bug report #1008210,
regarding cups-client: lp (-h) hostname option has to come before destination (-d)
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.)


-- 
1008210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008210
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups-client
Version: 2.3.3op2-3+deb11u1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where
appropriate ***

   * What led up to the situation?
	I tried to print an file with the lp command    * What exactly did you
do (or not do) that was effective (or ineffective)?
	I tried the command:
	lp -d DESTINATION -h HOSTNAME FILENAME    * What was the outcome of
this action?
	An error: lp: Error - The printer or class does not exist.
   * What outcome did you expect instead?
	printing of the file.

When I print with:
	lp -h HOSTNAME -d DESTINATION FILENAME
everything works ok, I'm sure cups-client on BUSTER did not care about
the placement of the host parameter. The man-page also reports
        lp  [  -E  ]  [  -U username ] [ -c ] [ -d
destination[/instance] ] [ -h host‐name[:port] ]
with the destination before the host-name

System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-12-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-client depends on:
ii  adduser      3.118
ii  cups-common  2.3.3op2-3+deb11u1
ii  libc6        2.31-13+deb11u2
ii  libcups2     2.3.3op2-3+deb11u1

cups-client recommends no packages.

Versions of packages cups-client suggests:
pn  cups       <none>
ii  cups-bsd   2.3.3op2-3+deb11u1
pn  smbclient  <none>

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Fri 25 Mar 2022 at 13:33:27 +0000, Brian Potkin wrote:

> forwarded 1008210 https://github.com/OpenPrinting/cups/issues/357
> tags 1008210 upstream
> thanks
> 
> 
> 
> On Thu 24 Mar 2022 at 12:53:14 +0100, Paul Hutschemaekers wrote:
> 
> > Package: cups-client
> > Version: 2.3.3op2-3+deb11u1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > *** Reporter, please consider answering these questions, where
> > appropriate ***
> > 
> >    * What led up to the situation?
> > 	I tried to print an file with the lp command    * What exactly did you
> > do (or not do) that was effective (or ineffective)?
> > 	I tried the command:
> > 	lp -d DESTINATION -h HOSTNAME FILENAME    * What was the outcome of
> > this action?
> > 	An error: lp: Error - The printer or class does not exist.
> >    * What outcome did you expect instead?
> > 	printing of the file.
> > 
> > When I print with:
> > 	lp -h HOSTNAME -d DESTINATION FILENAME
> > everything works ok, I'm sure cups-client on BUSTER did not care about
> > the placement of the host parameter. The man-page also reports
> >         lp  [  -E  ]  [  -U username ] [ -c ] [ -d
> > destination[/instance] ] [ -h host‐name[:port] ]
> > with the destination before the host-name
> 
> Thank you for your report, Paul. I can repeat your observations. Hence
> forwarded upstream.

This issue was dealt with upstream in CUPS v2.4.2 by a documentation
fix. Hence closing in Debian.

Cheers,

Brian.

--- End Message ---
Reply to: