Your message dated Tue, 06 May 2014 23:03:50 +0000
with message-id <[email protected]>
and subject line Bug#589991: fixed in mime-support 3.55
has caused the Debian Bug report #589991,
regarding mime-support: MIME types needed for x-gzip and x-compress
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 [email protected]
immediately.)


-- 
589991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589991
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mime-support
Version: 3.48-1

The mime.types file is missing MIME types for x-gzip and x-compress.
The debian mime.types file states:

#  Note: Compression schemes like "gzip", "bzip", and "compress" are
#  not actually "mime-types".  They are "encodings" and hence must
#  _not_ have entries in this file to map their extensions.  

I will systematically prove that (depending on semantics) either this
is outright false, or that the term "encoding" has been
misappropriated and, in the context of MIME, excluding these on the
basis that they are "encodings" is completely inappropriate. 

A file that has been gzipped contains data, and is a particular type
of file: a compressed archive.  An archive of what, MIME has no way to
know, and no reason to care.  It matters only that it is a gzip
archive.  In order for MUAs to handle such files suitably when
attached to a MIME e-mail, it must be possible for those mailers to
identify the type of file that has been attached.  Without a MIME
type, MUAs are expected to assume that an attached file is plain text
(see RFC 2045, section 5.2).  A gzip archive file is not plain text,
and may or may not consist of compressed plain text, though the latter
fact is actually completely irrelevant.

The MIME standard does contain the concept of a transfer encoding, of
which a compressed archive file is not.  MIME encodings exist to
facilitate transfer of non-ASCII data over e-mail, however this is the
only context in which an encoding is relevant to MIME (see RFC 2045,
sections 5 and 6, for example).

The primary purpose of file compression is to archive data in a
smaller amount of space than it otherwise would consume.  It's true
that compressing the file constitutes an "encoding" -- but then the
same is true of encoding music as MP3, images as PNG, HTML-formatted
text, etc.  In fact all data represented on a computer, regardless of
the type of data intended to be represented, constitute an encoding of
data.  These do not constitute transfer encodings, as their main
purpose is not to facilitate the transfer of data.  They are, as is a
gzip archive, merely data types which MIME was intended to accomodate.
It's also true that compressing data in some way facilitates transfer,
but this is not its main goal.  Further, as with all of the above
examples, compressing a file with gzip *does not* fulfill the purpose
of the transfer encoding with respect to MIME.  Once the file is
encoded with gzip, it is *still unsuitable for transfer* and must
subsequently be re-encoded using one of the transfer encoding schemes
specifically defined in the MIME standards.

Additionally, a gzip archive provides no means to identify the type of
content that is encoded.  All that one can be sure of is that the data
so provided can be reprocessed by gzip to uncompress it.  The MIME
standards likewise currently provide nothing suitable for e-mail
clients to convey this information.  For these reasons, it is only
suitable for MIME handlers to treat such files as application data,
which can be processed by the gzip program, as MIME was always
intended to be used. 

Finally, the MIME standards dictate that files not marked with an
associated Content-Type (MIME type) be asssumed to be plain text (RFC
2045 sect. 5.2).  This clearly is unacceptable for gzipped data, as it
is quite certainly invalid plain text.  As such, it *must* have a
suitable MIME type associated with it.

Please add MIME types for gzip and compress archive files.

Thanks

-- 
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D

Attachment: pgpRpaCkQU89W.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: mime-support
Source-Version: 3.55

We believe that the bug you reported is fixed in the latest version of
mime-support, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Charles Plessy <[email protected]> (supplier of updated mime-support package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 07 May 2014 07:03:23 +0900
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.55
Distribution: unstable
Urgency: low
Maintainer: Mime-Support Maintainers <[email protected]>
Changed-By: Charles Plessy <[email protected]>
Description: 
 mime-support - MIME files 'mime.types' & 'mailcap', and support programs
Closes: 77985 314952 384161 418564 458691 589991 623384 634254 674670 682900 
688872 691247 720619 723708 727156 727171 727173 745153 747050
Changes: 
 mime-support (3.55) unstable; urgency=low
 .
   * Media types removed:
 .
   92def2a application/x-font-woff       Closes: #727156
   c1797d2 application/x-md5             Closes: #720619
   fad5967 application/x-sha1            Closes: #720619
   a71f2b0 text/x-vcard                  Closes: #674670
 .
   * Media types added:
 .
   0d95409 application/font-sfnt
   0d95409 application/font-tdpfr
   0f12ec4 application/font-woff
   020388a application/gzip              Closes: #589991, 688872
   77eee72 application/oebps-package+xml    See: #712054
   ae8262a application/x-font-pcf        Closes: #727171
   020388a application/zlib              Closes: #589991, 688872
   a71f2b0 text/vcard                    Closes: #674670
 .
   * Changed associations of file suffixes with media types:
 .
   ae8262a application/x-font: removed pcf extensions.
   46df3ed application/vnd.visio: added vst vsw vss
   1a69660 application/x-ns-proxy-autoconfig: removed dat, Closes: #418564
 .
   * Packaging:
 .
   b016fe8 Remove “see” alternative for “view”.
           Thanks to Kevin Ryde <[email protected]>, Closes: #623384, #458691
   c5b794b Removed obsolete removal of /usr/doc/mime-support.
 .
   * update-mime:
 .
   5448676 Accept file names with alphanumeric characters from the current
           locale.  Thanks to Tomás <[email protected]>, Closes: #682900
   2a2243e Handle the “%c” (caption) field code from Desktop entry files.
           Thanks to Philipp Matthias Hahn <[email protected]>, Closes: #745153
   c0e8e69 Handle the “%i” (icon) field code from Desktop entry files.
   5cf809c Stop quoting “%s” when building /etc/mailcap from the files in
           /usr/lib/mime/packages.
           Thanks to Peter Chubb <[email protected]>, Closes: #747050
   f18b89f Warn when mailcap.order refers to packages that do not provide
           mailcap files.  Closes: #314952
   7b1947f Reject lines that do not start with a media type.  Closes: #384161
           This drops support for continuation lines in /usr/lib/mime/packages/.
 .
   * run-mailcap:
 .
   3c3b56c Redirect stdin to the tty when a mailcap entry says needsterminal.
           Thanks Kevin Ryde <[email protected]>, Closes: #727173
   80a1bc7 Remove unreliable permission check. Closes: #691247 thanks to
           Martin Mares <[email protected]> and Kevin Ryde <[email protected]>.
   e833a8a Stricter pattern for detection of manual pages.
           Thanks to Philipp Janda, LP: #1300484
   40f72a7 Force the use of a temporary alias for files containing a space in
           their name. Closes: #723708 thanks to Kevin Ryde <[email protected]>.
   642d6a9 Remind of RFC 1524 in the “SEE ALSO” section of mailcap(5) man page.
           Closes: #634254
   dd293ec Run the “file“ command when extension does not tell the media type.
           Thanks to Reuben Thomas <[email protected]>, Closes: #77985
   56dba74 Remove last-resort guesses of crontabs and man pages.
Checksums-Sha1: 
 2bbb86d8dbdbfc4ba876a06c2879a58c01467a7d 1608 mime-support_3.55.dsc
 264588eb050e93bf243269b9ad5adbf5d78794d3 34047 mime-support_3.55.tar.gz
 0bfd6d68e9cbc47dd199c2acd4e698f8c82cc57c 35080 mime-support_3.55_all.deb
Checksums-Sha256: 
 934a219caeea21da0c700713b86d550e709e75c6868a11369fc8ed4b57dca151 1608 
mime-support_3.55.dsc
 1f3ee631f640a4611be8d10f467bfae2f99ce73b872c63a7207d8ff513afa9cf 34047 
mime-support_3.55.tar.gz
 2aeda999617b33476a45c6c33fcc84bd0ce2ac0670030633dad5addacc587deb 35080 
mime-support_3.55_all.deb
Files: 
 935f16ca1afdf2cd437ab89a52b9f2a8 35080 net standard mime-support_3.55_all.deb
 2e8874031a44b9408736ed9cfad52749 1608 net standard mime-support_3.55.dsc
 76212d9bc9598e7444478868f8505103 34047 net standard mime-support_3.55.tar.gz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJTaWaXAAoJEMW9bI8ildUCbAUP/jC9ssli9JXKh4NYPbYNJ2Zp
rcYVJdgbQd1NEOo2uht3secSVbNw8D6RwjVubynbT8XSXmzqcJg7UllrF2LyuHHJ
7hCPDqYFT05x5+jVkMdSy78g50yg5NPSj+99QgxFjCRZmcZD37uYFEWi51+xGOw6
rO+IyCK2CWhF76rm5m2KwzQQ5nb8r2kSd6RdgFsZx6s34UdBUZvXlFw/FFvk1iHW
syRUqs1TLisSL7imGgDEri/3MJr8XR1wHF6lIFkp6vaOFp3PO8QPS2VBz0oy/Vx9
Ua1ZsNnohKVmDZIig+MZ34l/K1Skf7E3uErweDMi1yx8kTZPkrRTAboNGjF3ztgc
IPsGARRxvmkcRwlb/w75lVzaCEWTGFPfpn/0Ut4XNBuQDEGVjXoZBGjJwpRpf1BN
zG43x7r+uAbWvQRV7VfiF7P2qVJL11DUs7gxCU5+82drkBABxSqKgFzKP3L0QjSR
MIMWtJOUNJnEqjapCHsyMYkNirL1QNtb6PYIDSL6mRAKTfAU3jQ/k3V+9pztZLu7
unMlRLIqZuGK/6veiiO1x5sqG0MFg3ByHU8YbtBQui9SEH3+iOabtPjdbdbTYbFf
EGCrbBJ/Rb85CunIw40UJ7DFvesQRPFnBL/yfkggtwwD21w0VlR37y9JdNhQOt98
VDp6f+cx4iWC1lqXT1aT
=LnQj
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to