Your message dated Tue, 2 Sep 2014 19:30:52 +0200 with message-id <CAJGOOk-rNxEgpgh--Mch9wET00ZTJs0m_vSvHv2h3_YMxm=7...@mail.gmail.com> and subject line Re: s3cmd: Man page: --default-mime-type documentation incomplete has caused the Debian Bug report #691547, regarding s3cmd: Man page: --default-mime-type documentation incomplete 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.) -- 691547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691547 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: s3cmd Version: 1.1.0~beta3-1 Severity: minor Dear Maintainer, The s3cmd man page is incomplete where it reads: --default-mime-type Default MIME-type for stored objects. Application default is binary/octet-stream. As written, this is completely meaningless. One has no idea what it does even after reading it several times or reading the entire man page, especially since there are no examples which use the flag. Attempts to supply an argument either as '--default-mime-type=text/html' or as '--default-mime-type text/html' fail without further explanation. Consulting the Python source didn't immediately explain how 'default_mime_type' ever gets set to something other than 'binary/octet-stream'. After a good deal of Googling and some oblique mentions and a lucky guess that 's3cmd --dump-config | grep mime' might be informative, I learned that what this is trying to convey is that 'default_mime_type' (a name undocumented in the man page) is set in ~/.s3cfg, and anyone wishing to change the default MIME type without hardwiring every file uploaded (as '--mime-type=text/html' would), must specify the alternative MIME type in the config file and must then also give --default-mime-type on the CLI. The man page, at the very least, should mention the variable name and how it must be set in the config file before the option has any use. Better yet, it would also take an optional argument specifying the MIME type as a user would expect. -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages s3cmd depends on: ii python 2.7.3~rc2-1 s3cmd recommends no packages. s3cmd suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Hi. > After a good deal of Googling and some oblique mentions and a lucky guess that > 's3cmd --dump-config | grep mime' might be informative, I learned that what > this > is trying to convey is that 'default_mime_type' (a name undocumented in the > man page) > is set in ~/.s3cfg, and anyone wishing to change the default MIME type > without hardwiring > every file uploaded (as '--mime-type=text/html' would), must specify the > alternative > MIME type in the config file and must then also give --default-mime-type on > the CLI. In 1.0~rc5 --default-mime-type option works as advertised in manpage, so I'm closing the bug report. Best regards, Mikhail Gusarov.
--- End Message ---
