Uploaded bash 2.05-2 (sparc) to ftp-master
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 9 Apr 2001 23:29:24 +0200
Source: bash
Binary: bash-doc bash bash-builtins
Architecture: sparc
Version: 2.05-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/SPARC Build Daemon <buildd@vore.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Description:
bash - The GNU Bourne Again SHell
bash-builtins - Bash loadable builtins - headers & examples
Changes:
bash (2.05-2) unstable; urgency=medium
.
* Tighten build dependency (fixes #93509). Only an issue for upgrades
from bash-2.05-0, therefore urgency=medium.
* Remove changelog from bash package (also in bash-doc). Reported as
#93446, #93454, #93455.
* Fixed in bash-2.04, wrong example in report (#33822).
* Documented behaviour (ulimit, #72898).
* Use of redirection for #92324.
* sed, awk, ... builtins should be provided by the specific package.
there are other ways to make system scripts faster (ash, perl,
python, ...) (#61648).
* Unable to reproduce #34977 submitted for version 2.02.1, bug submitter
didn't respond to inquiries. Closing ...
* http://metalab.unc.edu/pub/Linux/docs/HOWTO/other-formats/html_single/Text-Terminal-HOWTO.html
as explanation for C-s behaviour (#68387, not sure why I missed this
for so long).
* Part one of the report is Posix.2 behaviour; part 2 (cd-ing relatively
from a subdirectory into a specified root-level directory) already
fixed in bash-2.04. #65316.
* Closing #13645. "The `-l' option should never have been documented, and it
was a mistake to include it in the first place -- it screws up the grammar.
Old Bourne shells and test commands had it because there was no other
way to find the length of a variable's value. Since bash has
${#variable}, there's no need for it. POSIX.2 says, in the rationale,
that implementation is irregular and that the shell supports it directly
* Unable to reproduce #19211 submitted for version 2.01 in current
versions (2.04, 2.05).
* Close #2301, safe creation of temp files is documented in bash(1):
"If the redirection operator is >, and the noclobber option to the set
builtin has been enabled, the redirection will fail if the file whose
name results from the expansion of word exists and is a regular file.
If the redirection operator is >|, or the redirection operator is > and
the noclobber option to the set builtin command is not enabled, the
redirection is attempted even if the file named by word exists."
* Fixed upstream in 2.05: #84743.
* #76596: Bourne-style shells have always accepted multiple directory name
arguments to cd. If the user doesn't like it, have him define a shell
function (see README.Debian).
* bash already has enabled the system wide /etc/bash.bashrc (#82117).
* #88223: Starting bash with --posix, or -o posix, or as `sh', does make
the entire bash session posix-compliant (with the caveats noted in the
info manual). Posix-compliant does not mean `behaves exactly like
historical versions of sh', nor does it mean `does only what is in
the standard and nothing more'.
.
Posix says nothing about brace expansion, so whether or not bash does
brace expansion in posix mode has no bearing on posix compliance.
.
If you don't want brace expansion, use `set +o braceexpand' or
`set +B' or start bash with the `+B' option.
.
* Lower temporarily severity of #92455, so that this version can move
to testing. This bug exists in 2.04 as well, so we don't make things
worse.
* Apply upstream patch 1.
Files:
8fd6d4444c32cc2a3424fdde7a852cd7 365960 base required bash_2.05-2_sparc.deb
4107f4777922b1d82e2e2c4cd9a11a64 86958 utils optional bash-builtins_2.05-2_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Ben Collins <bcollins@debian.org>
iD8DBQE61nz5fNc/ZB4E7C0RAmoPAJ4igb9JFzk73iij2NL18MlSakx9qwCgu7+T
ZUAbdIxgSlACEsOuwKnuYVU=
=t2lq
-----END PGP SIGNATURE-----
Reply to: