Your message dated Sat, 23 Nov 2013 09:20:54 +0000
with message-id <[email protected]>
and subject line Bug#589991: fixed in mime-support 3.55~experimental1
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
pgpCl0sTfGChY.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mime-support
Source-Version: 3.55~experimental1
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: Sat, 23 Nov 2013 16:19:12 +0900
Source: mime-support
Binary: mime-support
Architecture: source all
Version: 3.55~experimental1
Distribution: experimental
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: 418564 589991 674670 688872 720619 727156
Changes:
mime-support (3.55~experimental1) experimental; urgency=low
.
0f12ec4 Added ‘application/font-woff’
92def2a Remove the deprecated ‘application/x-font-woff’ type.
Closes: #727156
46df3ed Added vst vsw vss extensions to ‘application/vnd.visio’.
1a69660 Stop associating ‘dat’ files with
‘application/x-ns-proxy-autoconfig’. Closes: #418564.
020388a Add ‘application/gzip’ and ‘application/zlib’ media types.
Closes: #589991, 688872.
77eee72 Added ‘application/oebps-package+xml’ for ‘opf’ suffixes.
See also http://bugs.debian.org/712054.
c1797d2 Removed ‘application/x-md5’, there is no evidence for use.
Closes: #720619
a71f2b0 Update ‘text/x-vcard‘ to ‘text/vcard’ and associate with the
‘vcard’ suffix. Closes: #674670
Checksums-Sha1:
000397e3a5f4e7e711189473f37cf3eeac4e27aa 1719
mime-support_3.55~experimental1.dsc
0d5c57e4c2a1c47e2581a287dc91790f04952c43 32707
mime-support_3.55~experimental1.tar.gz
2cff9534b8a170f94a1b5b2e59ce0fcc1a7b063b 33686
mime-support_3.55~experimental1_all.deb
Checksums-Sha256:
c05ceb6f87c54148a43d1d2b963f9661ce58cfd49f178da0bac77af95fbf8d47 1719
mime-support_3.55~experimental1.dsc
2911ca5de8dda67a8a4cc9ef70b27e8379dd40a50c3d6698fe086fea123b0e06 32707
mime-support_3.55~experimental1.tar.gz
eb7005ed45376d75fb0796cff62163e308f94b45a12068ee9adfaa2c0d24eade 33686
mime-support_3.55~experimental1_all.deb
Files:
918ecb4e839468fea32beb24aad1789f 1719 net standard
mime-support_3.55~experimental1.dsc
392b0bf5c7cc2fc37b20329084a45034 32707 net standard
mime-support_3.55~experimental1.tar.gz
1420cdc62dfce3ba79da107cbbd1e6c5 33686 net standard
mime-support_3.55~experimental1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iQIcBAEBCgAGBQJSkF5bAAoJEMW9bI8ildUCIl0P/2yQKh2p/LUq5tFujNTQ+IXO
AaKdK3m9L+9GVl0iMz0WJO9o3kxBeNGGfdjng/zLfOKgzbzMQiRMGEEFB+9zMQtE
G7VvCaXroCMmFw4CXpZOtukBnUYGoqPb3LD7E5aan1K58SxDxotPHhtVuW7kyPzy
s/Oa6bOsCNCpDOX2c1hhfKlBouI6y9+iLVjaW3XV180zpkAugwPsfmeJJRaW8+Np
lvjshOJUxjTFGOC4jMvS4KUcBrUVihhIaof/CrcXTu7Q5ITuFUYQ8QexT4gdhUY8
c6kbgNcCQpDBAsNx6jIwfP7C2vyXS1jY0GV1GIYCKLrzz/a8j/OSYRH8syZZTLqo
IzRG3RejeQGY6xAz3tSifMHklITFv6sLwwR5EW/5FyW80fLYzf7hbtbWv+PCsGJk
NjUBOT8fOBareNA8qB1zvh+fosrwZL/WHcLl5bjgzSQuuXIuYUhftKJ4uGciNe1c
//sfZM+rLioVgK9qYt2o4c6OorzwWlvIOkM4texWQ7ESd739CKY2HSjazbjj4yFH
Fm9g5qirfzjZgpeAurAoM+PzHTidVKBMur7G7LTjXlPAOeo5hdfFgpuW0+UlVv7Y
0OMb7VeSKSOY+az97uaf0k+21qgfr3N1pWrtZdkvfk36tXHfdX+J2rnAG75fF666
Cw8DMoe8KIKsvp+ceXYa
=bbfb
-----END PGP SIGNATURE-----
--- End Message ---
