[Pkg-cups-devel] Bug#365301: Discrepancy between CUPS lpr command and Users Manual

Jack Carroll mykrowatt at comcast.net
Mon May 1 02:37:22 UTC 2006


On Sun, Apr 30, 2006 at 06:05:47PM +0100, Roger Leigh wrote:
> 
> Make sure you are using the lpr from cupsys-bsd.

	You have narrowed down the bug.  The lpr command installed by etch
belongs to the lpr package, not to cupsys-bsd.  Nevertheless, the Etch
cupsys package shows cupsys-bsd as a "Suggests:" dependency, same as in
Sarge.  So aptitude should have installed it automatically when it installed
cupsys, because aptitude is supposed to install Recommends: and Suggests:
dependencies by default.
	This is definitely a bug, because it violates the CUPS Software
Users Manual, which states on page 9, "CUPS provides both the System V
(lp(1)) and Berkeley (lpr(1)) printing commands".  It then goes on to show
the CUPS syntax for each of these.
	The question now is what package the bug is in.  It could be in
aptitude, or it could be in tasksel, which installs the printing system.  To
investigate this, I commanded:
		aptitude install cupsys
which should have resolved the dependencies.  It displayed a message that
there were 0 packages to upgrade, 0 to install, 0 to remove, and 0 not
upgraded.
	Therefore the new bug is in aptitude, or possibly in one of its
config files.  Adding the -r command line option didn't change the behavior,
and the man page doesn't show an option to cause Suggests: dependencies to
be resolved.

	I was able to install the Suggests: dependencies manually.  The CUPS
lpr command worked after that, and interpreted the syntax correctly.

> 
> What syntax should be used in place of "-o raw" to send raw print data
> to lpr (assuming this is not a regression or the wrong lpr package)?

	Wouldn't know.  I was testing -o media=Middle.




More information about the Pkg-cups-devel mailing list