Your message dated Thu, 8 Oct 2015 20:27:03 +0200
with message-id <[email protected]>
and subject line Re: Bug#739099: vorbis-tools: ogg123 manpage inadequately
documents -d option
has caused the Debian Bug report #739099,
regarding vorbis-tools: ogg123 manpage inadequately documents -d option
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.)
--
739099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739099
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vorbis-tools
Version: 1.4.0-1
Severity: minor
Tags: upstream
The manpage briefly mentions the -d option, and says it takes such
choices as 'alsa'. It further mentions that the 'alsa' option has some
sub-parameters.
However, the manpage doesn't include a sufficiently-clear example or
explanation on how to build the actual value for the -d option to
contain these options. Are they comma-separated? Colons? Use name=value
or name:value, or what..?
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
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 vorbis-tools depends on:
ii libao4 1.1.0-2
ii libc6 2.17-97
ii libcurl3-gnutls 7.34.0-1
ii libflac8 1.3.0-2
ii libogg0 1.3.1-1
ii libspeex1 1.2~rc1.1-1
ii libvorbis0a 1.3.2-1.3
ii libvorbisenc2 1.3.2-1.3
ii libvorbisfile3 1.3.2-1.3
vorbis-tools recommends no packages.
vorbis-tools suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.4.0-1
On 08-12-2014 Martin Steghöfer wrote:
As I couldn't really confirm the lack of documentation that you
reported (see previous message [1]), it would be great, if you could
provide us with a little more details about how specifically we could
improve the documentation. Otherwise I'm afraid we cannot do anything
about it and have to close the bug report without changes to the package.
[1] https://bugs.debian.org/739099#10
Since (1) I fail to see the problem, (2) the original bug reporter
hasn't contributed any more information after 2 messages asking for
clarification (the first one being sent 11 months ago) and (3) no one
else speaks up about any ideas on the problem or possible solutions, I
am closing this bug.
Cheers,
Martin
--- End Message ---