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

Bug#273083: marked as done (lprm: check arguments)

Your message dated Tue, 21 May 2013 20:53:27 +0300 (EEST)
with message-id <20130521175327.78982C2832@sid.nuvreauspam>
and subject line Closing old bugs filed against cupsys (or related packages)
has caused the Debian Bug report #273083,
regarding lprm: check arguments
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

273083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273083
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cupsys-bsd
Version: 1.1.20final+rc1-1
Severity: minor
File: /usr/bin/lprm

$ lprm 33-44
just removes job 33. It should at least say something if it is given
unexpected arguments.

P.S., lpq shows all jobs are owned by me, but
$ lprm -
Password for jidanni on localhost? 
Password for jidanni on localhost? 
Password for jidanni on localhost? 
Password for jidanni on localhost? 
Password for jidanni on localhost? 
lprm: Unable to cancel job(s)!

Yes, each time I typed my passwd.
Same happens for "cancel -a".

OK, running
$ while lprm;do :;done #but twice though
cleaned up all the jobs I had queued.
-- System Information:
* cupsys-bsd/setuplpd: false

--- End Message ---
--- Begin Message ---
Version: 1.4.4-1


Some (long) time ago you filed this bug against cupsys or a related 
package. In the meantime the cupsys package has been renamed to cups and 
this bug was "lost". Since the bug is already quite old now it is being 

If the issue you encountered is still present in recent cups packages 
(as released with Debian 7.0 wheezy for example) the CUPS maintainers 
would very much appreciate a fresh report using:

    reportbug <package>

You should also mention the number of this bug if you think it contains 
valuable information.

Please note that further information sent to this bug is likely to 
remain unread, because the bug is currently not assigned to any existing 

Thank you for for trying to improve Debian by reporting bugs.

Kind regards,
Andrei (with no relation to CUPS maintenance)

--- End Message ---

Reply to: