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

Bug#81824: marked as done (cupsys-client: What about using the debian alternatives system for lpr?)

Your message dated Sat, 14 Jul 2007 16:21:28 +0300
with message-id <11fae7c70707140621s58309ad5g8389d5a905cd9d4b@mail.gmail.com>
and subject line cupsys: closing prehistoric bugs
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: cupsys-client
Version: 1.1.4-3
Severity: wishlist

Why does cupsys-client conflict with lpr and lprng? It would be much better for the 
three packages to use the debian alternatives system, so that for example (at least) 
the server-side cupsys and lprng could be both installed at the same time on the 
same computer. This way, one could have several cups queues that all send processed
data to a raw lprng queue (what lprng calls a bounce queue). This way, I could define 
say 3 different queues using the same printer with different default setups (e.g. grayscale, 
low resolution colour and high resolution colour) and send all bounce processed data to 
a "raw" queue that orderly spools it. In this way the three high level queues do not try to 
access directly the physical device and can be used simultaneously, while the low level 
queue takes care to orderly spool the processed data and sends them to the printer.

Otherwise, (this should probably be done upstream) it could be made possible to easily 
define a "raw" printer within cups, that just takes files and dumps them to the specified
printer, with no processing at all.

Finally: I am currently using the gimp-print printer drivers for CUPS, which work 
beautifully. Would you mind packaging them? I would gladly help you, although I am not 
a debian developer, perhaps sending you the (trivial) patches to install the files at their 
correct positions in a debian system.

Bye
Giacomo Mulas

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux capitanata 2.4.0 #4 Mon Jan 8 13:10:59 CET 2001 i686 unknown

Versions of the packages cupsys-client depends on:
ii  libc6          2.2-10         GNU C Library: Shared libraries and Timezone
ii  libcupsys2     1.1.4-3        Common UNIX Printing System(tm) - libs
ii  libpam0g       0.72-12        Pluggable Authentication Modules library
ii  zlib1g         1.1.3-12       compression library - runtime
	^^^ (Provides virtual package libz1)

--- End Message ---
--- Begin Message --- 
As per decision of the Debian CUPS maintenance team, we are hereby
closing bugs concerning release 1.1.4, as they are dating back from
over 6 years ago.

Since then, CUPS has evolved into 1.1.23 (present in Debian 3.1 Sarge)
and 1.2.x generations (present since Debian 4.0 Etch), so we feel that
the issue reported simply cannot be addressed anymore.

Feel free to reopen this bug if you feel that it was closed in error
and explain why.

--
Martin-Éric Racine
http://q-funk.iki.fi

--- End Message ---
Reply to: