Your message dated Tue, 3 Aug 2010 16:07:56 +0200 with message-id <AANLkTinkqMpG5Wve7D1JLvE8Rw+njjGiyRvSExH06x_g@mail.gmail.com> and subject line [Debian QA] please review your old bug reports against CUPS has caused the Debian Bug report #365301, regarding Discrepancy between CUPS lpr command and Users Manual 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.) -- 365301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=365301 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Discrepancy between CUPS lpr command and Users Manual
- From: Jack Carroll <mykrowatt@comcast.net>
- Date: Fri, 28 Apr 2006 23:10:06 -0400
- Message-id: <20060429031005.GB796@chives.local>
Package: cupsys Version: 1.1.23-12 This report is for the version of cupsys currently installed by etch. The version installed by sarge behaves differently. The Software Users Manual says the lpr command has the same -o options as the lp command. For the past several years, that was true. Starting with this version, the lpr command rejects the -o argument as a syntax error. The lpr man page agrees with this behavior. For the version installed by sarge, the -o option worked on lpr, but the man page didn't show it. It appears that CUPS has reverted the lpr command syntax to emulate the old BSD lpr command, but has not updated the Users Manual to reflect this change.
--- End Message ---
--- Begin Message ---Hi,
- To: 365301-done@bugs.debian.org
- Subject: [Debian QA] please review your old bug reports against CUPS
- From: Jean Felder <jean.felder@gmail.com>
- Date: Tue, 3 Aug 2010 16:07:56 +0200
- Message-id: <AANLkTinkqMpG5Wve7D1JLvE8Rw+njjGiyRvSExH06x_g@mail.gmail.com>
This bug is quite old and I didn't get any answer from my previous mail.
So, I'm closing this bug report.
If the problem still occurs, please, feel free to reopen it.
Thanks,
Jean
--- End Message ---