Your message dated Sun, 21 Feb 2010 13:35:18 +0000
with message-id <[email protected]>
and subject line Bug#411261: fixed in sharutils 1:4.8-1
has caused the Debian Bug report #411261,
regarding sharutils: uudecode(1) suggestions
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.)
--
411261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411261
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sharutils
Version: 1:4.6.3-0
Severity: minor
Tags: patch
Thank you for recently fixing some very old issues with this manpage.
May I make a further suggestion?
I think the main paragraph for uuencode is currently quite unclear and
also inaccurate. Unclear because of the future tense combined with jumping
between the description of encoding and decoding. Inaccurate, because _name_
is only a *suggestion* ("uudecode -o" can override the name).
How about the following text instead?
Uuencode reads _file_ (or by default the standard input) and writes an
encoded version to the standard output, using only printing ASCII
characters. The encoded output begins with a header, for use by uudecode,
which records the mode of the input file and suggests _name_ for the
decoded file that will be created. (If _name_ is /dev/stdout then
uudecode will decode to standard output.) The encoding has the format
documented at uuencode(5), unless the option -m is given, when base64
encoding is used instead.
I attach a fairly small patch for this.
Actually, would you consider a patch for bigger changes?
For a start, the manpage should use fonts in a more standard way.
More importantly, I think BUGS should list something like this:
o uudecode silently overwrites _name_ if it exists already
o uudecode accepts names like ../foo
Thus, users would at least be warned that they should always inspect the
header lines or use the -o option.
(If you judge that this belongs upstream, I'd be grateful if you could
forward it, thank you.)
Yours,
(Dr) Jeremy Bygott
Oxford
-- System Information:
Debian Release: 4.0
--- uuencode.1.exp 2007-02-17 12:15:16.035662000 +0000
+++ uuencode.1.new 2007-02-17 16:31:20.535903808 +0000
@@ -45,8 +45,8 @@
.I Uuencode
and
.I uudecode
-are used to transmit binary files over transmission mediums
-that do not support other than simple
+are used to transmit binary files over channels
+that support only simple
ASCII
data.
.PP
@@ -54,22 +54,23 @@
reads
.I file
(or by default the standard input) and writes an encoded version
-to the standard output.
-The encoding uses only printing
+to the standard output, using only printing
ASCII
-characters and includes the
-mode of the file and the operand
+characters. The encoded output begins with a header, for use by
+.IR uudecode ,
+which records the mode of the input file and suggests
.I name
-for use by
-.I uudecode.
-If
+for the decoded file that will be created. (If
.I name
is
.I /dev/stdout
-the result will be written to standard output. By default the standard
-UU encoding format will be used. If the option
+then
+.I uudecode
+will decode to standard output.) The encoding has the format
+documented at uuencode(5), unless
+the option
.I \-m
-is given on the command line
+is given, when
.B base64
encoding is used instead.
.PP
@@ -96,8 +97,8 @@
.I name
is /dev/stdout the result will be written to standard output.
.I Uudecode
-ignores any leading and trailing lines. The program can automatically decide
-which of the both supported encoding schemes are used.
+ignores any leading and trailing lines. The program tells from the
+header which of the two supported encoding schemes was used.
.SH EXAMPLES
The following example packages up a source tree, compresses it,
uuencodes it and mails it to a user on another system.
--- End Message ---
--- Begin Message ---
Source: sharutils
Source-Version: 1:4.8-1
We believe that the bug you reported is fixed in the latest version of
sharutils, which is due to be installed in the Debian FTP archive:
sharutils-doc_4.8-1_all.deb
to main/s/sharutils/sharutils-doc_4.8-1_all.deb
sharutils_4.8-1.debian.tar.gz
to main/s/sharutils/sharutils_4.8-1.debian.tar.gz
sharutils_4.8-1.dsc
to main/s/sharutils/sharutils_4.8-1.dsc
sharutils_4.8-1_amd64.deb
to main/s/sharutils/sharutils_4.8-1_amd64.deb
sharutils_4.8.orig.tar.bz2
to main/s/sharutils/sharutils_4.8.orig.tar.bz2
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.
Santiago Vila <[email protected]> (supplier of updated sharutils 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: SHA256
Format: 1.8
Date: Sun, 21 Feb 2010 14:05:14 +0100
Source: sharutils
Binary: sharutils sharutils-doc
Architecture: source all amd64
Version: 1:4.8-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila <[email protected]>
Changed-By: Santiago Vila <[email protected]>
Description:
sharutils - shar, unshar, uuencode, uudecode
sharutils-doc - Documentation for GNU sharutils
Closes: 411261
Changes:
sharutils (1:4.8-1) unstable; urgency=low
.
* New upstream release, now under GPL version 3 or later.
* Use strip, not "install -s", to make lintian happy.
* Modified debian/rules to support cross-build.
* Drop gettext and texinfo from build-depends.
* Changed "Suggests:" to "bsd-mailx | mailx".
* Improved uudecode(1). Closes: #411261.
* Added homepage field to control file.
* Switch to 3.0 (quilt) source format.
* Added missing compress-dummy(1).
Checksums-Sha1:
d090321eaf5e496134189b371eabe2c35955104c 1343 sharutils_4.8-1.dsc
ede5ec0c676f0f0997691f0d34f4c6992aba9c43 926526 sharutils_4.8.orig.tar.bz2
1da916849ab27ea029fca6992a38967781c9bd46 7865 sharutils_4.8-1.debian.tar.gz
0d124331694bf99ee763394930faf3cf3c505f70 42656 sharutils-doc_4.8-1_all.deb
2e74bc38eff1599dc6f5f93fb1314fceef1c6769 198214 sharutils_4.8-1_amd64.deb
Checksums-Sha256:
a617a18db51a3533539c5cb0bad7193754b47cadf05130b3d01b50343377186c 1343
sharutils_4.8-1.dsc
d532fbde62ffb5d712eb1c7e317a314d8f3fa4c73a8752d53a6ea44cf95fd4a6 926526
sharutils_4.8.orig.tar.bz2
a3ecd3f4dea88447a4c84257d0844360866f86f97f7b507accc75bab61eb69eb 7865
sharutils_4.8-1.debian.tar.gz
5b473827304500cfdd31871994c0a4a87d8f3534c6ef1d87cb31835a7fe08328 42656
sharutils-doc_4.8-1_all.deb
44e933690ae05e8dd465cd6fb508930099fe831a7b5ca83233e12b692bf3de38 198214
sharutils_4.8-1_amd64.deb
Files:
7e22ca27996a4c260b6879353282708a 1343 utils optional sharutils_4.8-1.dsc
1fc05a1ab6c3ba3b663ff8d8364aa7ce 926526 utils optional
sharutils_4.8.orig.tar.bz2
f3e8ed8f81ec983825146cd0db0844ed 7865 utils optional
sharutils_4.8-1.debian.tar.gz
6079fcd9abd96e99a3a07b85a63f4edc 42656 doc optional sharutils-doc_4.8-1_all.deb
3d50b28088f8f35445133189d278f20b 198214 utils optional
sharutils_4.8-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBCAAGBQJLgTKbAAoJEEHOfwufG4syvR8H/j7T6AujUaQE6l21S1QQogV/
72eeIxj1vghGhtEEdDnQlhofTXu39ikLTgZIOiiBoNzAenmkhuQS6j9BU38o8n+j
tG4D0CgevfXdvPy/rKmtVC6vM6lp0oHQLco0Oh2hktKSV9aDybgiKgfahEFL3BE7
KoqEbidWrKXA1wvaAlOMrCGzmLRqLERloYgg8AV9S8pn3dmJ4XMWWwaA4FE+sF8O
5NNQSTFfMYAKV87MfMz5mbrHQyOSvRU9ZGXDTuA4gcRZS+bbUH79yxsSYU5WIdfz
qLLVG98xRwzvTVkX9+8xwlUKYXoZeOXtYvQJk98bhEPpp0U3uaBwV2JlT4ITqSw=
=ynQ+
-----END PGP SIGNATURE-----
--- End Message ---
