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

Bug#445330: marked as done (cupsys: mime.types(5) is confusingly named)

Your message dated Wed, 8 Mar 2017 19:48:38 +0000
with message-id <08032017194630.9af7a95c42a7@desktop.copernicus.org.uk>
and subject line Re: Bug#445330: cupsys: mime.types(5) is confusingly named
has caused the Debian Bug report #445330,
regarding cupsys: mime.types(5) is confusingly named
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.)


-- 
445330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445330
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cupsys
Version: 1.3.2-1
Severity: normal

I thought at first that mime.types(5) referred to /etc/mime.types, but
it doesn't. Could it please be renamed so that it's obvious it is to
do with CUPS's mime.types file and not the system-wide one?

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'experimental'), (600, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cupsys depends on:
ii  adduser                 3.105            add and remove users and groups
ii  cupsys-common           1.3.2-1          Common UNIX Printing System(tm) - 
ii  debconf [debconf-2.0]   1.5.14           Debian configuration management sy
ii  gs-esp                  8.15.3.dfsg.1-1  The Ghostscript PostScript interpr
ii  libavahi-compat-libdnss 0.6.21-2         Avahi Apple Bonjour compatibility 
ii  libc6                   2.6.1-1+b1       GNU C Library: Shared libraries
ii  libcupsimage2           1.3.2-1          Common UNIX Printing System(tm) - 
ii  libcupsys2              1.3.2-1          Common UNIX Printing System(tm) - 
ii  libdbus-1-3             1.1.1-3          simple interprocess messaging syst
ii  libgnutls13             1.7.19-1         the GNU TLS library - runtime libr
ii  libkrb53                1.6.dfsg.1-7     MIT Kerberos runtime libraries
ii  libldap2                2.1.30.dfsg-13.5 OpenLDAP libraries
ii  libpam0g                0.99.7.1-4       Pluggable Authentication Modules l
ii  libpaper1               1.1.22           library for handling paper charact
ii  libslp1                 1.2.1-6.2        OpenSLP libraries
ii  lsb-base                3.1-24           Linux Standard Base 3.1 init scrip
ii  perl-modules            5.8.8-7          Core Perl modules
ii  procps                  1:3.2.7-4.1      /proc file system utilities
ii  ssl-cert                1.0.14           Simple debconf wrapper for openssl
ii  xpdf-utils [poppler-uti 3.02-1.1         Portable Document Format (PDF) sui

Versions of packages cupsys recommends:
ii  cups-pdf              2.4.6-4            PDF printer for CUPS
ii  cupsys-client         1.3.2-1            Common UNIX Printing System(tm) - 
ii  foomatic-filters      3.0.2-20061031-1.2 linuxprinting.org printer support 
ii  smbclient             3.0.26a-1          a LanManager-like simple client fo

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
On Fri 05 Oct 2007 at 01:34:47 +0100, Reuben Thomas wrote:

> Package: cupsys
> Version: 1.3.2-1
> Severity: normal
> 
> I thought at first that mime.types(5) referred to /etc/mime.types, but
> it doesn't. Could it please be renamed so that it's obvious it is to
> do with CUPS's mime.types file and not the system-wide one?

Enhancement requests are always welcome in the BTS. However, after
nearly ten years and no response it is probably unrealistic to expect
the request to be fulfilled any time soon. The question becomes - should
we carry this bug in the BTS indefinitely? I think not; hence closing.
Sorry.

Regards,

--

--- End Message ---
Reply to: