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

Bug#702925: marked as done (Replace cups-specific mime.types/libcupsmime with libmagic)

Your message dated Wed, 8 Mar 2017 19:53:30 +0000
with message-id <08032017195101.4337ae9b0b31@desktop.copernicus.org.uk>
and subject line Re: Bug#702925: Replace cups-specific mime.types/libcupsmime with libmagic
has caused the Debian Bug report #702925,
regarding Replace cups-specific mime.types/libcupsmime with libmagic
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.)


-- 
702925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702925
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups
Version: 1.5.3-2.15
Severity: wishlist
File: /usr/share/cups/mime/mime.types
Tags: upstream

I came across mime.types / libcupsmime and my immediate reaction is
"why is cups doing this, when libmagic already provides a perfectly
good library and database of MIME type heuristics?"

There's probably a reason, but I couldn't work it out from a brief
search.  I'm creating this ticket in case nobody has ever thought of
this before.

--- End Message ---
--- Begin Message --- 
On Wed 13 Mar 2013 at 12:42:08 +1100, Trent W. Buck wrote:

> Package: cups
> Version: 1.5.3-2.15
> Severity: wishlist
> File: /usr/share/cups/mime/mime.types
> Tags: upstream
> 
> I came across mime.types / libcupsmime and my immediate reaction is
> "why is cups doing this, when libmagic already provides a perfectly
> good library and database of MIME type heuristics?"
> 
> There's probably a reason, but I couldn't work it out from a brief
> search.  I'm creating this ticket in case nobody has ever thought of
> this before.

Enhancement requests are always welcome in the BTS. However, after four
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,

--
Brian.

--- End Message ---
Reply to: