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

Bug#610430: marked as done (cups-client: cupsaddsmb: Need an ability to specify drivers to install)



Your message dated Tue, 25 Feb 2014 17:18:18 +0100
with message-id <2952154.7zxITFJVOV@gyllingar>
and subject line Re: Bug#610430: cups-client: cupsaddsmb: Need an ability to specify drivers to install
has caused the Debian Bug report #610430,
regarding cups-client: cupsaddsmb: Need an ability to specify drivers to install
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.)


-- 
610430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610430
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cups-client
Version: 1.4.4-7
Severity: normal
File: /usr/sbin/cupsaddsmb

cups-client ships usefull tool cupsaddsmb. It allows to upload some
driver's file to samba server and link printer to driver.

Out of the box it looks in /usr/share/cups/drivers for cups ps drivers.
But 
1)this driver isn't shipped with debian
2)this driver couldn't be shipped (it doesn't work without dll from M$)
  at least in main
3)this tool doesn't provide user any option to specify which driver to
  install (As I've seen in docs it could be CUPS's one, M$ one or Adobe
  one) and where files are located (User shouldn't put anything under
  /usr/share.)

I suggest this tool should have 2 options to specify:
* which driver to install
* path to driver files

-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (620, 'testing'), (610, 'proposed-updates'), (610, 'stable'), (600, 'unstable'), (580, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-xen-686 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cups-client depends on:
ii  adduser                 3.112+nmu2       add and remove users and groups
ii  cups-common             1.4.4-7          Common UNIX Printing System(tm) - 
ii  libc6                   2.11.2-7         Embedded GNU C Library: Shared lib
ii  libcups2                1.4.4-7          Common UNIX Printing System(tm) - 
ii  libcupsimage2           1.4.4-7          Common UNIX Printing System(tm) - 
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

cups-client recommends no packages.

Versions of packages cups-client suggests:
ii  cups             1.4.4-7                 Common UNIX Printing System(tm) - 
ii  cups-bsd         1.4.4-7                 Common UNIX Printing System(tm) - 
pn  cups-pt          <none>                  (no description available)
pn  gtklp            <none>                  (no description available)
ii  kdeprint         4:3.5.9.dfsg.1-6+lenny1 print system for KDE
pn  xpp              <none>                  (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi Alexander, and thanks for your bugreport,

Le mardi, 18 janvier 2011, 16.23:51 Alexander Gerasiov a écrit :
> cups-client ships usefull tool cupsaddsmb. It allows to upload some
> driver's file to samba server and link printer to driver.
> 
> Out of the box it looks in /usr/share/cups/drivers for cups ps
> drivers. But
> 1)this driver isn't shipped with debian
> 2)this driver couldn't be shipped (it doesn't work without dll from
> M$) at least in main
> 3)this tool doesn't provide user any option to specify which driver to
> install (As I've seen in docs it could be CUPS's one, M$ one or Adobe
> one) and where files are located (User shouldn't put anything under
> /usr/share.)
> 
> I suggest this tool should have 2 options to specify:
> * which driver to install
> * path to driver files

This is all documented in cupsaddsmb manpage, closing the bugreport.

OdyX

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply to: