Report forwarded to debian-bugs-dist@lists.debian.org, Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>:
Bug#10494; Package dpkg.   debian-bugs-dist@lists.debian.orgKlee Dienes and Ian Jackson  Subject: Bug#10494: dpkg "setup" method prints spurious messages Reply-To: Miquel van Smoorenburg , 10494@bugs.debian.org Resent-From: Miquel van Smoorenburg Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Klee Dienes and Ian Jackson Resent-Date: Wed, 11 Jun 1997 09:18:02 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: dpkg X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by bugs@bugs.debian.org id=B.86601997922687 (code B ref -1); Wed, 11 Jun 1997 09:18:02 GMT Message-ID: <19970611110444.61413@cistron.nl> Date: Wed, 11 Jun 1997 11:04:44 +0200 From: Miquel van Smoorenburg To: submit@bugs.debian.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.71 Package: dpkg Version: 1.4.0.8 When used with bash-2.0, the dpkg disk setup method prints spurious messages: /usr/lib/dpkg/methods/disk/setup: line 8: 16632 Broken pipe find "$mountpoint$2" -follow -name '*.deb' -print 2>/dev/null 16633 Done | head -1 16634 Done | grep . >/dev/null Using `/pub/debian/stable/binary-i386' as main binary dir. Using `/pub/debian/stable/binary-i386/Packages.gz' for main. Using `/pub/debian/contrib/binary-i386' as contrib binary dir. Using `/pub/debian/contrib/binary-i386/Packages.gz' for contrib. /usr/lib/dpkg/methods/disk/setup: line 8: 16638 Broken pipe find "$mountpoint$2" -follow -name '*.deb' -print 2>/dev/null 16639 Done | head -1 16640 Done | grep . >/dev/null Using `/pub/debian/non-free/binary-i386' as non-free binary dir. Using `/pub/debian/non-free/binary-i386/Packages.gz' for non-free. This is probably a bug in bash-2.0, but a fast way to fix it in the setup shell script is like this: --- methods/disk/setup.orig Wed Jun 11 11:35:57 1997 +++ methods/disk/setup Wed Jun 11 12:01:53 1997 @@ -429,12 +429,15 @@ echo "\`$2' does not exist." return fi + exec 3>&2 2>/dev/null if ! find "$mountpoint$2" -follow -name '*.deb' -print \ 2>/dev/null | head -1 | grep . >/dev/null + exec 2>&3 3>&- then echo "\`$2' does not contain any *.deb packages. Hmmpf." return fi + exec 2>&3 3>&- echo "Using \`$2' as $1 binary dir." this_binary="$2" } It is possible that the other methods have a similar bug, but I can't test this at the moment. It would be nice to fix this in Debian-1.3.1 Mike. -- | Miquel van Smoorenburg | "I need more space" "Well, why not move to Texas" | | miquels@cistron.nl | "No, on my account, stupid." "Stupid? Uh-oh.." | | PGP fingerprint: FE 66 52 4F CD 59 A5 36 7F 39 8B 20 F1 D6 74 02 |   Acknowledgement sent to Miquel van Smoorenburg <miquels@cistron.nl>:
New bug report received and forwarded. Copy sent to Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: Miquel van Smoorenburg Subject: Bug#10494: Acknowledgement (was: dpkg "setup" method prints spurious messages) Message-ID: In-Reply-To: <19970611110444.61413@cistron.nl> References: <19970611110444.61413@cistron.nl> X-Debian-PR-Message: ack 10494 Thank you for the problem report you have sent regarding Debian Linux. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the developers' mailing list for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Klee Dienes and Ian Jackson If you wish to submit further information on your problem, please send it to 10494@bugs.debian.org (and *not* to bugs@bugs.debian.org). Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at submit) by bugs.debian.org; 11 Jun 1997 09:06:19 +0000 Received: (qmail 22683 invoked from network); 11 Jun 1997 09:06:18 -0000 Received: from Q.cistron.nl (miquels@195.64.65.23) by master.debian.org with SMTP; 11 Jun 1997 09:06:17 -0000 Received: (from miquels@localhost) by Q.cistron.nl (8.8.5/8.8.5) id LAA08534; Wed, 11 Jun 1997 11:04:44 +0200 Message-ID: <19970611110444.61413@cistron.nl> Date: Wed, 11 Jun 1997 11:04:44 +0200 From: Miquel van Smoorenburg To: submit@bugs.debian.org Subject: dpkg "setup" method prints spurious messages Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.71 Package: dpkg Version: 1.4.0.8 When used with bash-2.0, the dpkg disk setup method prints spurious messages: /usr/lib/dpkg/methods/disk/setup: line 8: 16632 Broken pipe find "$mountpoint$2" -follow -name '*.deb' -print 2>/dev/null 16633 Done | head -1 16634 Done | grep . >/dev/null Using `/pub/debian/stable/binary-i386' as main binary dir. Using `/pub/debian/stable/binary-i386/Packages.gz' for main. Using `/pub/debian/contrib/binary-i386' as contrib binary dir. Using `/pub/debian/contrib/binary-i386/Packages.gz' for contrib. /usr/lib/dpkg/methods/disk/setup: line 8: 16638 Broken pipe find "$mountpoint$2" -follow -name '*.deb' -print 2>/dev/null 16639 Done | head -1 16640 Done | grep . >/dev/null Using `/pub/debian/non-free/binary-i386' as non-free binary dir. Using `/pub/debian/non-free/binary-i386/Packages.gz' for non-free. This is probably a bug in bash-2.0, but a fast way to fix it in the setup shell script is like this: --- methods/disk/setup.orig Wed Jun 11 11:35:57 1997 +++ methods/disk/setup Wed Jun 11 12:01:53 1997 @@ -429,12 +429,15 @@ echo "\`$2' does not exist." return fi + exec 3>&2 2>/dev/null if ! find "$mountpoint$2" -follow -name '*.deb' -print \ 2>/dev/null | head -1 | grep . >/dev/null + exec 2>&3 3>&- then echo "\`$2' does not contain any *.deb packages. Hmmpf." return fi + exec 2>&3 3>&- echo "Using \`$2' as $1 binary dir." this_binary="$2" } It is possible that the other methods have a similar bug, but I can't test this at the moment. It would be nice to fix this in Debian-1.3.1 Mike. -- | Miquel van Smoorenburg | "I need more space" "Well, why not move to Texas" | | miquels@cistron.nl | "No, on my account, stupid." "Stupid? Uh-oh.." | | PGP fingerprint: FE 66 52 4F CD 59 A5 36 7F 39 8B 20 F1 D6 74 02 |   Information forwarded to debian-bugs-dist@lists.debian.org, Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>:
Bug#10494; Package dpkg.   debian-bugs-dist@lists.debian.orgKlee Dienes and Ian Jackson  Subject: Bug#10494: dpkg "setup" method prints spurious messages Reply-To: miquels@cistron.nl (Miquel van Smoorenburg), 10494@bugs.debian.org Resent-From: miquels@cistron.nl (Miquel van Smoorenburg) Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Klee Dienes and Ian Jackson Resent-Date: Wed, 11 Jun 1997 12:48:00 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: dpkg X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by bugs@bugs.debian.org id=B.86603316424582 (code B ref -1); Wed, 11 Jun 1997 12:48:00 GMT To: submit@bugs.debian.org Path: not-for-mail From: miquels@cistron.nl (Miquel van Smoorenburg) Newsgroups: lists.debian.bugs Date: 11 Jun 1997 14:44:26 +0200 Organization: Cistron Internet Services B.V. Lines: 39 Message-ID: <5nm6ja$8pm$1@Q.cistron.nl> References: <19970611110444.61413@cistron.nl> In article <19970611110444.61413@cistron.nl>, Miquel van Smoorenburg wrote: >Package: dpkg >Version: 1.4.0.8 > >When used with bash-2.0, the dpkg disk setup method prints spurious messages: > [...] >This is probably a bug in bash-2.0, but a fast way to fix it in the >setup shell script is like this: I sent in the wrong patch (as I found out 2 minutes later..). Here's a correct one: --- methods/disk/setup.orig Wed Jun 11 11:35:57 1997 +++ methods/disk/setup Wed Jun 11 12:25:47 1997 @@ -429,12 +429,15 @@ echo "\`$2' does not exist." return fi + exec 3>&2 2>/dev/null if ! find "$mountpoint$2" -follow -name '*.deb' -print \ 2>/dev/null | head -1 | grep . >/dev/null then + exec 2>&3 3>&- echo "\`$2' does not contain any *.deb packages. Hmmpf." return fi + exec 2>&3 3>&- echo "Using \`$2' as $1 binary dir." this_binary="$2" } Mike. -- | Miquel van Smoorenburg | "I need more space" "Well, why not move to Texas" | | miquels@cistron.nl | "No, on my account, stupid." "Stupid? Uh-oh.." | | PGP fingerprint: FE 66 52 4F CD 59 A5 36 7F 39 8B 20 F1 D6 74 02 |   Acknowledgement sent to miquels@cistron.nl (Miquel van Smoorenburg):
Extra info received and forwarded to list. Copy sent to Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: miquels@cistron.nl (Miquel van Smoorenburg) Subject: Bug#10494: Info received (was Bug#10494: dpkg "setup" method prints spurious messages) Message-ID: In-Reply-To: <5nm6ja$8pm$1@Q.cistron.nl> References: <5nm6ja$8pm$1@Q.cistron.nl> X-Debian-PR-Message: ack-info-maintonly 10494 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers' mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Klee Dienes and Ian Jackson If you wish to continue to submit further information on your problem, please send it to 10494@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at submit) by bugs.debian.org; 11 Jun 1997 12:46:04 +0000 Received: (qmail 24578 invoked from network); 11 Jun 1997 12:46:04 -0000 Received: from Q.cistron.nl (miquels@195.64.65.23) by master.debian.org with SMTP; 11 Jun 1997 12:46:02 -0000 Received: (from miquels@localhost) by Q.cistron.nl (8.8.5/8.8.5) id OAA09015 for submit@bugs.debian.org; Wed, 11 Jun 1997 14:44:26 +0200 To: submit@bugs.debian.org Path: not-for-mail From: miquels@cistron.nl (Miquel van Smoorenburg) Newsgroups: lists.debian.bugs Subject: Re: Bug#10494: dpkg "setup" method prints spurious messages Date: 11 Jun 1997 14:44:26 +0200 Organization: Cistron Internet Services B.V. Lines: 39 Message-ID: <5nm6ja$8pm$1@Q.cistron.nl> References: <19970611110444.61413@cistron.nl> In article <19970611110444.61413@cistron.nl>, Miquel van Smoorenburg wrote: >Package: dpkg >Version: 1.4.0.8 > >When used with bash-2.0, the dpkg disk setup method prints spurious messages: > [...] >This is probably a bug in bash-2.0, but a fast way to fix it in the >setup shell script is like this: I sent in the wrong patch (as I found out 2 minutes later..). Here's a correct one: --- methods/disk/setup.orig Wed Jun 11 11:35:57 1997 +++ methods/disk/setup Wed Jun 11 12:25:47 1997 @@ -429,12 +429,15 @@ echo "\`$2' does not exist." return fi + exec 3>&2 2>/dev/null if ! find "$mountpoint$2" -follow -name '*.deb' -print \ 2>/dev/null | head -1 | grep . >/dev/null then + exec 2>&3 3>&- echo "\`$2' does not contain any *.deb packages. Hmmpf." return fi + exec 2>&3 3>&- echo "Using \`$2' as $1 binary dir." this_binary="$2" } Mike. -- | Miquel van Smoorenburg | "I need more space" "Well, why not move to Texas" | | miquels@cistron.nl | "No, on my account, stupid." "Stupid? Uh-oh.." | | PGP fingerprint: FE 66 52 4F CD 59 A5 36 7F 39 8B 20 F1 D6 74 02 |   Information forwarded to debian-bugs-dist@lists.debian.org, Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>:
Bug#10494; Package dpkg.   debian-bugs-dist@lists.debian.orgKlee Dienes and Ian Jackson  Subject: Bug#10494: dpkg "setup" method prints spurious messages Reply-To: Miquel van Smoorenburg , 10494@bugs.debian.org Resent-From: Miquel van Smoorenburg Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Klee Dienes and Ian Jackson Resent-Date: Wed, 11 Jun 1997 12:48:04 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: dpkg X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 10494-bugs@bugs.debian.org id=B10494.86603316424580 (code B ref 10494); Wed, 11 Jun 1997 12:48:04 GMT Date: Wed, 11 Jun 1997 14:44:26 +0200 From: Miquel van Smoorenburg Message-Id: <199706111244.OAA09022@Q.cistron.nl> To: 10494@bugs.debian.org Newsgroups: lists.debian.bugs References: <19970611110444.61413@cistron.nl> Organization: Cistron Internet Services B.V. In article <19970611110444.61413@cistron.nl>, Miquel van Smoorenburg wrote: >Package: dpkg >Version: 1.4.0.8 > >When used with bash-2.0, the dpkg disk setup method prints spurious messages: > [...] >This is probably a bug in bash-2.0, but a fast way to fix it in the >setup shell script is like this: I sent in the wrong patch (as I found out 2 minutes later..). Here's a correct one: --- methods/disk/setup.orig Wed Jun 11 11:35:57 1997 +++ methods/disk/setup Wed Jun 11 12:25:47 1997 @@ -429,12 +429,15 @@ echo "\`$2' does not exist." return fi + exec 3>&2 2>/dev/null if ! find "$mountpoint$2" -follow -name '*.deb' -print \ 2>/dev/null | head -1 | grep . >/dev/null then + exec 2>&3 3>&- echo "\`$2' does not contain any *.deb packages. Hmmpf." return fi + exec 2>&3 3>&- echo "Using \`$2' as $1 binary dir." this_binary="$2" } Mike. -- | Miquel van Smoorenburg | "I need more space" "Well, why not move to Texas" | | miquels@cistron.nl | "No, on my account, stupid." "Stupid? Uh-oh.." | | PGP fingerprint: FE 66 52 4F CD 59 A5 36 7F 39 8B 20 F1 D6 74 02 |   Acknowledgement sent to Miquel van Smoorenburg <miquels@cistron.nl>:
Extra info received and forwarded to list. Copy sent to Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: Miquel van Smoorenburg Subject: Bug#10494: Info received (was Bug#10494: dpkg "setup" method prints spurious messages) Message-ID: In-Reply-To: <199706111244.OAA09022@Q.cistron.nl> References: <199706111244.OAA09022@Q.cistron.nl> X-Debian-PR-Message: ack-info-maintonly 10494 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers' mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Klee Dienes and Ian Jackson If you wish to continue to submit further information on your problem, please send it to 10494@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at 10494) by bugs.debian.org; 11 Jun 1997 12:46:04 +0000 Received: (qmail 24577 invoked from network); 11 Jun 1997 12:46:02 -0000 Received: from Q.cistron.nl (miquels@195.64.65.23) by master.debian.org with SMTP; 11 Jun 1997 12:46:02 -0000 Received: (from miquels@localhost) by Q.cistron.nl (8.8.5/8.8.5) id OAA09022; Wed, 11 Jun 1997 14:44:26 +0200 Date: Wed, 11 Jun 1997 14:44:26 +0200 From: Miquel van Smoorenburg Message-Id: <199706111244.OAA09022@Q.cistron.nl> To: 10494@bugs.debian.org Newsgroups: lists.debian.bugs Subject: Re: Bug#10494: dpkg "setup" method prints spurious messages References: <19970611110444.61413@cistron.nl> Organization: Cistron Internet Services B.V. In article <19970611110444.61413@cistron.nl>, Miquel van Smoorenburg wrote: >Package: dpkg >Version: 1.4.0.8 > >When used with bash-2.0, the dpkg disk setup method prints spurious messages: > [...] >This is probably a bug in bash-2.0, but a fast way to fix it in the >setup shell script is like this: I sent in the wrong patch (as I found out 2 minutes later..). Here's a correct one: --- methods/disk/setup.orig Wed Jun 11 11:35:57 1997 +++ methods/disk/setup Wed Jun 11 12:25:47 1997 @@ -429,12 +429,15 @@ echo "\`$2' does not exist." return fi + exec 3>&2 2>/dev/null if ! find "$mountpoint$2" -follow -name '*.deb' -print \ 2>/dev/null | head -1 | grep . >/dev/null then + exec 2>&3 3>&- echo "\`$2' does not contain any *.deb packages. Hmmpf." return fi + exec 2>&3 3>&- echo "Using \`$2' as $1 binary dir." this_binary="$2" } Mike. -- | Miquel van Smoorenburg | "I need more space" "Well, why not move to Texas" | | miquels@cistron.nl | "No, on my account, stupid." "Stupid? Uh-oh.." | | PGP fingerprint: FE 66 52 4F CD 59 A5 36 7F 39 8B 20 F1 D6 74 02 |   Information forwarded to debian-bugs-dist@lists.debian.org, Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>:
Bug#10494; Package dpkg.   debian-bugs-dist@lists.debian.orgKlee Dienes and Ian Jackson  Subject: Bug#10494: dpkg "setup" method prints spurious messages Reply-To: Guy Maor , 10494@bugs.debian.org Resent-From: Guy Maor Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Klee Dienes and Ian Jackson Resent-Date: Wed, 11 Jun 1997 15:48:05 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: dpkg X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 10494-bugs@bugs.debian.org id=B10494.86604331228458 (code B ref 10494); Wed, 11 Jun 1997 15:48:05 GMT To: 10494@bugs.debian.org References: <19970611110444.61413@cistron.nl> From: Guy Maor Date: 11 Jun 1997 10:33:23 -0500 In-Reply-To: Miquel van Smoorenburg's message of Wed, 11 Jun 1997 11:04:44 +0200 Message-ID: <872069duik.fsf@slip-124-3.ots.utexas.edu> Lines: 13 X-Mailer: Gnus v5.3/Emacs 19.34 Miquel van Smoorenburg writes: > When used with bash-2.0, the dpkg disk setup method prints spurious messages: > > /usr/lib/dpkg/methods/disk/setup: line 8: 16632 Broken pipe find "$mountpoint$2" -follow -name '*.deb' -print 2>/dev/null A better way to get rid of unwanted broken pipe messages is to install an empty handler for SIGPIPE. For example: (trap {} SIGPIPE; find .) | head -1 Guy   Acknowledgement sent to Guy Maor <maor@ece.utexas.edu>:
Extra info received and forwarded to list. Copy sent to Klee Dienes and Ian Jackson <dpkg-maint@chiark.greenend.org.uk>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: Guy Maor Subject: Bug#10494: Info received (was Bug#10494: dpkg "setup" method prints spurious messages) Message-ID: In-Reply-To: <872069duik.fsf@slip-124-3.ots.utexas.edu> References: <872069duik.fsf@slip-124-3.ots.utexas.edu> X-Debian-PR-Message: ack-info-maintonly 10494 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers' mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Klee Dienes and Ian Jackson If you wish to continue to submit further information on your problem, please send it to 10494@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at 10494) by bugs.debian.org; 11 Jun 1997 15:35:12 +0000 Received: (qmail 28456 invoked from network); 11 Jun 1997 15:35:11 -0000 Received: from slip-79-16.ots.utexas.edu (root@128.83.254.176) by master.debian.org with SMTP; 11 Jun 1997 15:35:11 -0000 Received: by slip-79-16.ots.utexas.edu id m0wbpOm-000GGaC (Debian Smail-3.2 1996-Jul-4 #2); Wed, 11 Jun 1997 10:33:24 -0500 (CDT) To: 10494@bugs.debian.org Subject: Re: Bug#10494: dpkg "setup" method prints spurious messages References: <19970611110444.61413@cistron.nl> From: Guy Maor Date: 11 Jun 1997 10:33:23 -0500 In-Reply-To: Miquel van Smoorenburg's message of Wed, 11 Jun 1997 11:04:44 +0200 Message-ID: <872069duik.fsf@slip-124-3.ots.utexas.edu> Lines: 13 X-Mailer: Gnus v5.3/Emacs 19.34 Miquel van Smoorenburg writes: > When used with bash-2.0, the dpkg disk setup method prints spurious messages: > > /usr/lib/dpkg/methods/disk/setup: line 8: 16632 Broken pipe find "$mountpoint$2" -follow -name '*.deb' -print 2>/dev/null A better way to get rid of unwanted broken pipe messages is to install an empty handler for SIGPIPE. For example: (trap {} SIGPIPE; find .) | head -1 Guy   Merged 10259 10433 10494. Request was from Ian Jackson <ijackson@chiark.greenend.org.uk> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 6 Sep 1997 00:29:08 +0000 Received: (qmail 6827 invoked from network); 6 Sep 1997 00:29:07 -0000 Received: from chiark.greenend.org.uk (root@chiark.greenend.org.uk@195.224.76.132) by 205.229.104.5 with SMTP; 6 Sep 1997 00:29:07 -0000 Received: by chiark.greenend.org.uk id m0x78kc-0004oGC (Debian /\oo/\ Smail3.1.29.1 #29.37); Sat, 6 Sep 97 01:29 BST Message-Id: Date: Sat, 6 Sep 97 01:29 BST From: Ian Jackson To: Debian bugs control server Subject: dpkg bug severities merge 2904 9833 severity 957 wishlist severity 1555 wishlist merge 1797 5639 6842 6843 7956 severity 1797 grave severity 1921 wishlist retitle 2701 conffiles purge / directory removal ordering bug merge 2701 2911 7012 8391 11047 close 2894 close 11073 reassign 11074 dpkg-ftp severity 11228 wishlist merge 11246 11385 close 2929 close 3225 close 3406 close 3407 close 4093 reassign 4319 netbase severity 4448 wishlist merge 4451 4449 1037 6394 6709 6757 7093 11868 severity 11992 wishlist merge 12187 11341 severity 11341 wishlist retitle 12505 /usr/doc/dpkg/{internals,index}.html identical reassign 4515 perl merge 4474 1037 close 4561 close 4584 # binary file diffs: merge 4588 4628 6871 reassign 4784 general close 4808 close 4848 merge 4863 3170 close 4877 close 4936 retitle 4974 dpkg -s exit status 0 for nonexistent package retitle 5380 dselect does not support frozen distribution merge 9355 5380 merge 4895 5450 close 10049 severity 10091 wishlist severity 10452 wishlist merge 10433 10259 10494 reassign 10259 bash close 5640 close 5733 merge 6007 1399 close 6383 close 6435 close 6452 close 6482 severity 6486 wishlist close 6736 severity 7128 wishlist severity 7389 wishlist severity 7540 wishlist reassign 7606 dpkg-ftp severity 7692 wishlist reassign 7813 dpkg-ftp reassign 8554 dpkg-ftp severity 8639 wishlist close 8893 reassign 9217 dpkg-mountable retitle 5807 dpkg-source .tmp-nest bug merge 4641 5807 severity 5983 wishlist retitle 5868 syslogd/start-stop-daemon/TERM handling retitle 5536 dpkg-deb --no-check problem reassign 4895 dpkg-ftp severity 4950 wishlist severity 4588 wishlist severity 1037 wishlist   Bug reassigned from package `dpkg' to `bash'. Request was from Ian Jackson <ijackson@chiark.greenend.org.uk> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 6 Sep 1997 00:29:08 +0000 Received: (qmail 6827 invoked from network); 6 Sep 1997 00:29:07 -0000 Received: from chiark.greenend.org.uk (root@chiark.greenend.org.uk@195.224.76.132) by 205.229.104.5 with SMTP; 6 Sep 1997 00:29:07 -0000 Received: by chiark.greenend.org.uk id m0x78kc-0004oGC (Debian /\oo/\ Smail3.1.29.1 #29.37); Sat, 6 Sep 97 01:29 BST Message-Id: Date: Sat, 6 Sep 97 01:29 BST From: Ian Jackson To: Debian bugs control server Subject: dpkg bug severities merge 2904 9833 severity 957 wishlist severity 1555 wishlist merge 1797 5639 6842 6843 7956 severity 1797 grave severity 1921 wishlist retitle 2701 conffiles purge / directory removal ordering bug merge 2701 2911 7012 8391 11047 close 2894 close 11073 reassign 11074 dpkg-ftp severity 11228 wishlist merge 11246 11385 close 2929 close 3225 close 3406 close 3407 close 4093 reassign 4319 netbase severity 4448 wishlist merge 4451 4449 1037 6394 6709 6757 7093 11868 severity 11992 wishlist merge 12187 11341 severity 11341 wishlist retitle 12505 /usr/doc/dpkg/{internals,index}.html identical reassign 4515 perl merge 4474 1037 close 4561 close 4584 # binary file diffs: merge 4588 4628 6871 reassign 4784 general close 4808 close 4848 merge 4863 3170 close 4877 close 4936 retitle 4974 dpkg -s exit status 0 for nonexistent package retitle 5380 dselect does not support frozen distribution merge 9355 5380 merge 4895 5450 close 10049 severity 10091 wishlist severity 10452 wishlist merge 10433 10259 10494 reassign 10259 bash close 5640 close 5733 merge 6007 1399 close 6383 close 6435 close 6452 close 6482 severity 6486 wishlist close 6736 severity 7128 wishlist severity 7389 wishlist severity 7540 wishlist reassign 7606 dpkg-ftp severity 7692 wishlist reassign 7813 dpkg-ftp reassign 8554 dpkg-ftp severity 8639 wishlist close 8893 reassign 9217 dpkg-mountable retitle 5807 dpkg-source .tmp-nest bug merge 4641 5807 severity 5983 wishlist retitle 5868 syslogd/start-stop-daemon/TERM handling retitle 5536 dpkg-deb --no-check problem reassign 4895 dpkg-ftp severity 4950 wishlist severity 4588 wishlist severity 1037 wishlist   Information forwarded to debian-bugs-dist@lists.debian.org, Guy Maor <maor@debian.org>:
Bug#10494; Package bash.   debian-bugs-dist@lists.debian.orgGuy Maor  Subject: Bug#10494: 'Broken pipe' message is not a bug. Reply-To: Guy Maor , 10494@bugs.debian.org Resent-From: Guy Maor Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Guy Maor Resent-Date: Mon, 08 Sep 1997 11:18:02 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: bash X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 10494-bugs@bugs.debian.org id=B10494.8737170436168 (code B ref 10494); Mon, 08 Sep 1997 11:18:02 GMT To: 10494@bugs.debian.org, Ian Jackson From: Guy Maor Date: 08 Sep 1997 10:58:12 -0500 Message-ID: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> Lines: 9 X-Mailer: Gnus v5.3/Emacs 19.34 Ian, this is not a bug in bash. 'Broken pipe ...' messages are generated when a bash shell is killed with a SIGPIPE. This is a feature as SIGPIPE is usually an indication of an error. You can silence the error by sending the shell's stderr to /dev/null or by installing an empty SIGPIPE handler. Guy   Acknowledgement sent to Guy Maor <maor@ece.utexas.edu>:
Extra info received and forwarded to list. Copy sent to Guy Maor <maor@debian.org>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: Guy Maor Subject: Bug#10494: Info received (was 'Broken pipe' message is not a bug.) Message-ID: In-Reply-To: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> References: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> X-Debian-PR-Message: ack-info-maintonly 10494 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers' mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Guy Maor If you wish to continue to submit further information on your problem, please send it to 10494@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at 10494) by bugs.debian.org; 8 Sep 1997 11:10:43 +0000 Received: (qmail 6164 invoked from network); 8 Sep 1997 11:10:42 -0000 Received: from slip-110-30.ots.utexas.edu (HELO femto) (root@slip-110-30.ots.utexas.edu@128.83.190.30) by 205.229.104.5 with SMTP; 8 Sep 1997 11:10:42 -0000 Received: by femto id m0x86Ca-000GGZC (Debian Smail-3.2 1996-Jul-4 #2); Mon, 8 Sep 1997 10:58:12 -0500 (CDT) To: 10494@bugs.debian.org, Ian Jackson Subject: 'Broken pipe' message is not a bug. From: Guy Maor Date: 08 Sep 1997 10:58:12 -0500 Message-ID: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> Lines: 9 X-Mailer: Gnus v5.3/Emacs 19.34 Ian, this is not a bug in bash. 'Broken pipe ...' messages are generated when a bash shell is killed with a SIGPIPE. This is a feature as SIGPIPE is usually an indication of an error. You can silence the error by sending the shell's stderr to /dev/null or by installing an empty SIGPIPE handler. Guy   Information forwarded to debian-bugs-dist@lists.debian.org, Guy Maor <maor@debian.org>:
Bug#10494; Package bash.   debian-bugs-dist@lists.debian.orgGuy Maor  Subject: Bug#10494: 'Broken pipe' message is not a bug. Reply-To: Ian Jackson , 10494@bugs.debian.org Resent-From: Ian Jackson Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Guy Maor Resent-Date: Mon, 08 Sep 1997 12:48:04 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: bash X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 10494-bugs@bugs.debian.org id=B10494.87372240311749 (code B ref 10494); Mon, 08 Sep 1997 12:48:04 GMT Message-Id: Date: Mon, 8 Sep 97 18:27 BST From: Ian Jackson To: Guy Maor Cc: 10494@bugs.debian.org In-Reply-To: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> References: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> Guy Maor writes ("'Broken pipe' message is not a bug."): > Ian, this is not a bug in bash. 'Broken pipe ...' messages are > generated when a bash shell is killed with a SIGPIPE. This is a > feature as SIGPIPE is usually an indication of an error. I disagree. Most other and all naive programs simply die when they get SIGPIPE; bash should to the same. It is the responsibility of the calling program to notice an _unexpected_ SIGPIPE and report it if necessary. Unexpected means when the program isn't writing to a pipe, or possibly when the program on the other end of the pipe might legitimately not read all the input. bash has a misfeature, probably specified in POSIX, that commands of the form foo | bar | baz return the exit status of baz, without regard to that of foo or bar. However, this cannot be solved by having foo and bar complain if they get a SIGPIPE because (a) that doesn't help if foo or bar fail for some other reason and (b) foo or bar might legitimately get a SIGPIPE; in fact, a SIGPIPE in bar when baz exited with status 0, or a SIGPIPE in foo when bar did so or died due to a SIGPIPE, is probably OK. Therefore bash should act as follows: if baz exits with nonzero status including SIGPIPE, or foo or bar exit with nonzero status _excluding_ SIGPIPE then the overally command should have nonzero status, otherwise the whole command should have zero status. bash should print a message indicating the termination if baz gets a fatal signal, or if foo or bar get a fatal signal other than SIGPIPE. The behaviour of calling failures by earlier programs in the pipe errors is probably in contravention of POSIX and will probably cause some old unreliable scripts (ie ones which use pipes in ways where they are expecting some errors but can't detect which ones) to break rather than being unreliable. It should probably be disableable by using POSIXLY_CORRECT and/or a set option. > You can silence the error by sending the shell's stderr to /dev/null > or by installing an empty SIGPIPE handler. This is not a reasonable thing to have to do when SIGPIPE is usually expected and sane. Ian.   Acknowledgement sent to Ian Jackson <ijackson@chiark.greenend.org.uk>:
Extra info received and forwarded to list. Copy sent to Guy Maor <maor@debian.org>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: Ian Jackson Subject: Bug#10494: Info received (was 'Broken pipe' message is not a bug.) Message-ID: In-Reply-To: References: X-Debian-PR-Message: ack-info-maintonly 10494 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers' mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Guy Maor If you wish to continue to submit further information on your problem, please send it to 10494@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at 10494) by bugs.debian.org; 8 Sep 1997 12:40:03 +0000 Received: (qmail 11740 invoked from network); 8 Sep 1997 12:39:59 -0000 Received: from chiark.greenend.org.uk (root@chiark.greenend.org.uk@195.224.76.132) by 205.229.104.5 with SMTP; 8 Sep 1997 12:39:59 -0000 Received: by chiark.greenend.org.uk id m0x87bP-0004ocC (Debian /\oo/\ Smail3.1.29.1 #29.37); Mon, 8 Sep 97 18:27 BST Message-Id: Date: Mon, 8 Sep 97 18:27 BST From: Ian Jackson To: Guy Maor Cc: 10494@bugs.debian.org Subject: Re: 'Broken pipe' message is not a bug. In-Reply-To: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> References: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> Guy Maor writes ("'Broken pipe' message is not a bug."): > Ian, this is not a bug in bash. 'Broken pipe ...' messages are > generated when a bash shell is killed with a SIGPIPE. This is a > feature as SIGPIPE is usually an indication of an error. I disagree. Most other and all naive programs simply die when they get SIGPIPE; bash should to the same. It is the responsibility of the calling program to notice an _unexpected_ SIGPIPE and report it if necessary. Unexpected means when the program isn't writing to a pipe, or possibly when the program on the other end of the pipe might legitimately not read all the input. bash has a misfeature, probably specified in POSIX, that commands of the form foo | bar | baz return the exit status of baz, without regard to that of foo or bar. However, this cannot be solved by having foo and bar complain if they get a SIGPIPE because (a) that doesn't help if foo or bar fail for some other reason and (b) foo or bar might legitimately get a SIGPIPE; in fact, a SIGPIPE in bar when baz exited with status 0, or a SIGPIPE in foo when bar did so or died due to a SIGPIPE, is probably OK. Therefore bash should act as follows: if baz exits with nonzero status including SIGPIPE, or foo or bar exit with nonzero status _excluding_ SIGPIPE then the overally command should have nonzero status, otherwise the whole command should have zero status. bash should print a message indicating the termination if baz gets a fatal signal, or if foo or bar get a fatal signal other than SIGPIPE. The behaviour of calling failures by earlier programs in the pipe errors is probably in contravention of POSIX and will probably cause some old unreliable scripts (ie ones which use pipes in ways where they are expecting some errors but can't detect which ones) to break rather than being unreliable. It should probably be disableable by using POSIXLY_CORRECT and/or a set option. > You can silence the error by sending the shell's stderr to /dev/null > or by installing an empty SIGPIPE handler. This is not a reasonable thing to have to do when SIGPIPE is usually expected and sane. Ian.   Information forwarded to debian-bugs-dist@lists.debian.org, Guy Maor <maor@debian.org>:
Bug#10494; Package bash.   debian-bugs-dist@lists.debian.orgGuy Maor  Subject: Bug#10494: 'Broken pipe' message is not a bug. Reply-To: Guy Maor , 10494@bugs.debian.org Resent-From: Guy Maor Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Guy Maor Resent-Date: Tue, 09 Sep 1997 05:18:03 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: bash X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 10494-bugs@bugs.debian.org id=B10494.8737817062611 (code B ref 10494); Tue, 09 Sep 1997 05:18:03 GMT To: Ian Jackson Cc: 10494@bugs.debian.org References: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> From: Guy Maor Date: 09 Sep 1997 00:07:32 -0500 In-Reply-To: Ian Jackson's message of Mon, 8 Sep 97 18:27 BST Message-ID: <87k9gr6pnv.fsf@slip-110-30.ots.utexas.edu> Lines: 21 X-Mailer: Gnus v5.3/Emacs 19.34 Ian Jackson writes: > Most other and all naive programs simply die when they > get SIGPIPE; bash should to the same. I disagree, and I believe Chet will too. I will not make bash die from SIGPIPEs rather than ignore them. I'll keep this bug open if you wish, but I doubt that bash's default behavior will change. In my opinion, SIGPIPEs in a shell pipeline are more often a sign of an error than not, so bash's behavior is desirable. > bash has a misfeature, probably specified in POSIX, that commands of > the form This is a different problem which you've already reported as 7047. I've already communicated this request upstream. Guy   Acknowledgement sent to Guy Maor <maor@ece.utexas.edu>:
Extra info received and forwarded to list. Copy sent to Guy Maor <maor@debian.org>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: Guy Maor Subject: Bug#10494: Info received (was 'Broken pipe' message is not a bug.) Message-ID: In-Reply-To: <87k9gr6pnv.fsf@slip-110-30.ots.utexas.edu> References: <87k9gr6pnv.fsf@slip-110-30.ots.utexas.edu> X-Debian-PR-Message: ack-info-maintonly 10494 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers' mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Guy Maor If you wish to continue to submit further information on your problem, please send it to 10494@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at 10494) by bugs.debian.org; 9 Sep 1997 05:08:25 +0000 Received: (qmail 2599 invoked from network); 9 Sep 1997 05:07:59 -0000 Received: from slip-110-30.ots.utexas.edu (HELO femto) (root@slip-110-30.ots.utexas.edu@128.83.190.30) by 205.229.104.5 with SMTP; 9 Sep 1997 05:07:58 -0000 Received: by femto id m0x8IWU-000GGdC (Debian Smail-3.2 1996-Jul-4 #2); Tue, 9 Sep 1997 00:07:34 -0500 (CDT) To: Ian Jackson Cc: 10494@bugs.debian.org Subject: Re: 'Broken pipe' message is not a bug. References: <8790x794rv.fsf@slip-110-30.ots.utexas.edu> From: Guy Maor Date: 09 Sep 1997 00:07:32 -0500 In-Reply-To: Ian Jackson's message of Mon, 8 Sep 97 18:27 BST Message-ID: <87k9gr6pnv.fsf@slip-110-30.ots.utexas.edu> Lines: 21 X-Mailer: Gnus v5.3/Emacs 19.34 Ian Jackson writes: > Most other and all naive programs simply die when they > get SIGPIPE; bash should to the same. I disagree, and I believe Chet will too. I will not make bash die from SIGPIPEs rather than ignore them. I'll keep this bug open if you wish, but I doubt that bash's default behavior will change. In my opinion, SIGPIPEs in a shell pipeline are more often a sign of an error than not, so bash's behavior is desirable. > bash has a misfeature, probably specified in POSIX, that commands of > the form This is a different problem which you've already reported as 7047. I've already communicated this request upstream. Guy   Information forwarded to debian-bugs-dist@lists.debian.org, Guy Maor <maor@debian.org>:
Bug#10494; Package bash.   debian-bugs-dist@lists.debian.orgGuy Maor  Subject: Bug#10494: Bug#7047 and #10494: bash and pipes Reply-To: ian@chiark.greenend.org.uk, 10494@bugs.debian.org Resent-From: ian@chiark.greenend.org.uk Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Guy Maor Resent-Date: Fri, 12 Sep 1997 16:18:08 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: bash X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 10494-bugs@bugs.debian.org id=B10494.87408043819765 (code B ref 10494); Fri, 12 Sep 1997 16:18:08 GMT Message-Id: Date: Fri, 12 Sep 1997 17:05:44 +0100 (BST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: ian@chiark.greenend.org.uk To: 10494@bugs.debian.org, 7049@bugs.debian.org X-Mailer: VM 6.30 under Emacs 19.34.1 I think these two bugs are related, so I'm mailing both of them. Guy, feel free to merge them if you prefer. I think that the problem with bash printing what is IMO a spurious message may be due to the bash authors trying to fix the reliability problems with pipes, but not being clear about what those reliability problems are. Below is a transcript showing a number of examples of IMO broken behaviour. WRT 7047 (`bash documents no safe (easy) way to pipe'), you suggest to Chet Ramey that there be a shopt to make the exit status of a pipe be (effectively) that of the most-failing component in it. I think that this should be the default (unless you set POSIXLY_CORRECT or a special shell option). This will cause most existing scripts which rely on pipes and are currently unreliable to become reliable and functional. Scripts which use set -e and rely on the old ignored-status behaviour will break, but these are broken anyway (because they don't check for expected vs. unexpected failures of the early commands in the pipe). WRT 10494, you say that most broken pipes are due to errors. This may be true, but most _otherwise undetected_ broken pipes are not. A broken pipe occurs when the tail of a pipeline dies first, whether successfully or not. In most of the `programming error' cases the cause of the broken pipe is that the tail simply failed immediately or fairly quickly, and the correct diagnostics to issue are those relating to the tail command. The fact that this failure caused the earlier commands to die with broken pipe is not interesting, and reporting it will only serve to confuse. In the situation where the tail command in the pipe succeeded, but did not read all of the input available, it is usually the case that this situation is expected. Programs that do not read all of their input are quite common (head is the most common example), and the current policy of printing an error message whenever an earlier program fails makes programs like that almost impossible to use. Discarding stderr is obviously not a good solution. You suggest installing a SIGPIPE handler; however, this doesn't solve the problem. The program that gets the SIGPIPE (eg, in the example below, tar) doesn't trap SIGPIPE but just dies from it. The problem is that bash interprets this as a condition which warrants issuing a diagnostic but not setting the $? error indication, which is IMO inconsistent as well as not useful. bash should treat death due to SIGPIPE in a nonterminal program in a pipeline as a successful completion. Ian. -davenant:~/junk> cat t.sh #!/bin/sh set -e echo about to do pipe without head tar Ccf /dev - null | tar vvtf - | cat echo that seems to have worked - exit status $? echo echo about to do pipe with head tar Ccf / - usr/doc | tar vvtf - | head -1 echo that seems to have worked - exit status $? echo echo about to do pipe with false false | tar vvtf - | head -10 echo that seems to have worked - exit status $? echo echo about to do pipe with broken tar arguments tar --mumbledefumble | tar vvtf - | cat echo that seems to have worked - exit status $? -davenant:~/junk> ./t.sh about to do pipe without head crw-rw-rw- root/sys 1,3 May 28 01:49 1997 null ./t.sh: line 5: 27964 Broken pipe tar Ccf /dev - null 27965 Done | tar vvtf - 27966 Done | cat that seems to have worked - exit status 0 about to do pipe with head drwxr-xr-x root/root 0 Aug 5 02:32 1997 usr/doc/ ./t.sh: line 10: 27967 Broken pipe tar Ccf / - usr/doc 27968 | tar vvtf - 27969 Done | head -1 that seems to have worked - exit status 0 about to do pipe with false that seems to have worked - exit status 0 about to do pipe with broken tar arguments tar: unrecognized option `--mumbledefumble' Try `tar --help' for more information. that seems to have worked - exit status 0 -davenant:~/junk>   Acknowledgement sent to ian@chiark.greenend.org.uk:
Extra info received and forwarded to list. Copy sent to Guy Maor <maor@debian.org>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: ian@chiark.greenend.org.uk Subject: Bug#10494: Info received (was Bug#7047 and #10494: bash and pipes) Message-ID: In-Reply-To: References: X-Debian-PR-Message: ack-info-maintonly 10494 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers' mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Guy Maor If you wish to continue to submit further information on your problem, please send it to 10494@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at 10494) by bugs.debian.org; 12 Sep 1997 16:07:18 +0000 Received: (qmail 19759 invoked from network); 12 Sep 1997 16:07:15 -0000 Received: from gate.ncipher.com (HELO dover.ncipher.com) (root@gate.ncipher.com@195.224.55.2) by 205.229.104.5 with SMTP; 12 Sep 1997 16:07:15 -0000 Received: from scarp.ncipher.com (scarp.ncipher.com [195.224.55.134]) by dover.ncipher.com (8.7.6/8.7.3) with SMTP id RAA17681; Fri, 12 Sep 1997 17:19:47 +0100 Received: by scarp.ncipher.com id m0x9YE4-000yqOC (Debian Smail-3.2.0.94 1997-Apr-22 #1); Fri, 12 Sep 1997 17:05:44 +0100 (BST) Message-Id: Date: Fri, 12 Sep 1997 17:05:44 +0100 (BST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: ian@chiark.greenend.org.uk To: 10494@bugs.debian.org, 7049@bugs.debian.org Subject: Bug#7047 and #10494: bash and pipes X-Mailer: VM 6.30 under Emacs 19.34.1 I think these two bugs are related, so I'm mailing both of them. Guy, feel free to merge them if you prefer. I think that the problem with bash printing what is IMO a spurious message may be due to the bash authors trying to fix the reliability problems with pipes, but not being clear about what those reliability problems are. Below is a transcript showing a number of examples of IMO broken behaviour. WRT 7047 (`bash documents no safe (easy) way to pipe'), you suggest to Chet Ramey that there be a shopt to make the exit status of a pipe be (effectively) that of the most-failing component in it. I think that this should be the default (unless you set POSIXLY_CORRECT or a special shell option). This will cause most existing scripts which rely on pipes and are currently unreliable to become reliable and functional. Scripts which use set -e and rely on the old ignored-status behaviour will break, but these are broken anyway (because they don't check for expected vs. unexpected failures of the early commands in the pipe). WRT 10494, you say that most broken pipes are due to errors. This may be true, but most _otherwise undetected_ broken pipes are not. A broken pipe occurs when the tail of a pipeline dies first, whether successfully or not. In most of the `programming error' cases the cause of the broken pipe is that the tail simply failed immediately or fairly quickly, and the correct diagnostics to issue are those relating to the tail command. The fact that this failure caused the earlier commands to die with broken pipe is not interesting, and reporting it will only serve to confuse. In the situation where the tail command in the pipe succeeded, but did not read all of the input available, it is usually the case that this situation is expected. Programs that do not read all of their input are quite common (head is the most common example), and the current policy of printing an error message whenever an earlier program fails makes programs like that almost impossible to use. Discarding stderr is obviously not a good solution. You suggest installing a SIGPIPE handler; however, this doesn't solve the problem. The program that gets the SIGPIPE (eg, in the example below, tar) doesn't trap SIGPIPE but just dies from it. The problem is that bash interprets this as a condition which warrants issuing a diagnostic but not setting the $? error indication, which is IMO inconsistent as well as not useful. bash should treat death due to SIGPIPE in a nonterminal program in a pipeline as a successful completion. Ian. -davenant:~/junk> cat t.sh #!/bin/sh set -e echo about to do pipe without head tar Ccf /dev - null | tar vvtf - | cat echo that seems to have worked - exit status $? echo echo about to do pipe with head tar Ccf / - usr/doc | tar vvtf - | head -1 echo that seems to have worked - exit status $? echo echo about to do pipe with false false | tar vvtf - | head -10 echo that seems to have worked - exit status $? echo echo about to do pipe with broken tar arguments tar --mumbledefumble | tar vvtf - | cat echo that seems to have worked - exit status $? -davenant:~/junk> ./t.sh about to do pipe without head crw-rw-rw- root/sys 1,3 May 28 01:49 1997 null ./t.sh: line 5: 27964 Broken pipe tar Ccf /dev - null 27965 Done | tar vvtf - 27966 Done | cat that seems to have worked - exit status 0 about to do pipe with head drwxr-xr-x root/root 0 Aug 5 02:32 1997 usr/doc/ ./t.sh: line 10: 27967 Broken pipe tar Ccf / - usr/doc 27968 | tar vvtf - 27969 Done | head -1 that seems to have worked - exit status 0 about to do pipe with false that seems to have worked - exit status 0 about to do pipe with broken tar arguments tar: unrecognized option `--mumbledefumble' Try `tar --help' for more information. that seems to have worked - exit status 0 -davenant:~/junk>   Noted your statement that bug has been forwarded to bug-bash@prep.ai.mit.edu. Request was from Guy Maor <maor@ece.utexas.edu> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 29 Mar 1998 02:41:40 +0000 Received: (qmail 1813 invoked from network); 29 Mar 1998 02:41:39 -0000 Received: from 1cust109.max32.los-angeles.ca.ms.uu.net (root@153.34.86.109) by debian.novare.net with SMTP; 29 Mar 1998 02:41:39 -0000 Received: by ece.utexas.edu via sendmail from stdin id (Debian Smail3.2.0.101) for control@bugs.debian.org; Sat, 28 Mar 1998 18:42:22 -0800 (PST) To: control@bugs.debian.org Subject: c Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Guy Maor Date: 28 Mar 1998 18:42:21 -0800 Message-ID: <87iuoy2p6a.fsf@1Cust120.max37.los-angeles.ca.ms.uu.net> Lines: 5 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" forwarded 10259 bug-bash@prep.ai.mit.edu forwarded 10433 bug-bash@prep.ai.mit.edu forwarded 10494 bug-bash@prep.ai.mit.edu merge 10259 7047   Forwarded-to-address changed from bug-bash@prep.ai.mit.edu to bug-bash@prep.ai.mit.edu. Request was from Guy Maor <maor@ece.utexas.edu> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 29 Mar 1998 02:41:40 +0000 Received: (qmail 1813 invoked from network); 29 Mar 1998 02:41:39 -0000 Received: from 1cust109.max32.los-angeles.ca.ms.uu.net (root@153.34.86.109) by debian.novare.net with SMTP; 29 Mar 1998 02:41:39 -0000 Received: by ece.utexas.edu via sendmail from stdin id (Debian Smail3.2.0.101) for control@bugs.debian.org; Sat, 28 Mar 1998 18:42:22 -0800 (PST) To: control@bugs.debian.org Subject: c Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Guy Maor Date: 28 Mar 1998 18:42:21 -0800 Message-ID: <87iuoy2p6a.fsf@1Cust120.max37.los-angeles.ca.ms.uu.net> Lines: 5 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" forwarded 10259 bug-bash@prep.ai.mit.edu forwarded 10433 bug-bash@prep.ai.mit.edu forwarded 10494 bug-bash@prep.ai.mit.edu merge 10259 7047   Forwarded-to-address changed from bug-bash@prep.ai.mit.edu to bug-bash@prep.ai.mit.edu. Request was from Guy Maor <maor@ece.utexas.edu> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 29 Mar 1998 02:41:40 +0000 Received: (qmail 1813 invoked from network); 29 Mar 1998 02:41:39 -0000 Received: from 1cust109.max32.los-angeles.ca.ms.uu.net (root@153.34.86.109) by debian.novare.net with SMTP; 29 Mar 1998 02:41:39 -0000 Received: by ece.utexas.edu via sendmail from stdin id (Debian Smail3.2.0.101) for control@bugs.debian.org; Sat, 28 Mar 1998 18:42:22 -0800 (PST) To: control@bugs.debian.org Subject: c Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Guy Maor Date: 28 Mar 1998 18:42:21 -0800 Message-ID: <87iuoy2p6a.fsf@1Cust120.max37.los-angeles.ca.ms.uu.net> Lines: 5 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" forwarded 10259 bug-bash@prep.ai.mit.edu forwarded 10433 bug-bash@prep.ai.mit.edu forwarded 10494 bug-bash@prep.ai.mit.edu merge 10259 7047   Merged 7047 10259 10433 10494. Request was from Guy Maor <maor@ece.utexas.edu> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 29 Mar 1998 02:41:40 +0000 Received: (qmail 1813 invoked from network); 29 Mar 1998 02:41:39 -0000 Received: from 1cust109.max32.los-angeles.ca.ms.uu.net (root@153.34.86.109) by debian.novare.net with SMTP; 29 Mar 1998 02:41:39 -0000 Received: by ece.utexas.edu via sendmail from stdin id (Debian Smail3.2.0.101) for control@bugs.debian.org; Sat, 28 Mar 1998 18:42:22 -0800 (PST) To: control@bugs.debian.org Subject: c Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Guy Maor Date: 28 Mar 1998 18:42:21 -0800 Message-ID: <87iuoy2p6a.fsf@1Cust120.max37.los-angeles.ca.ms.uu.net> Lines: 5 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" forwarded 10259 bug-bash@prep.ai.mit.edu forwarded 10433 bug-bash@prep.ai.mit.edu forwarded 10494 bug-bash@prep.ai.mit.edu merge 10259 7047   Information forwarded to debian-bugs-dist@lists.debian.org, Guy Maor <maor@debian.org>:
Bug#10494; Package bash.   debian-bugs-dist@lists.debian.orgGuy Maor  Subject: Bug#10494: comment from upstream author Reply-To: Matthias Klose , 10494@bugs.debian.org Resent-From: Matthias Klose Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Guy Maor Resent-Date: Sat, 20 Nov 1999 17:48:33 GMT Resent-Message-ID: Resent-Sender: owner@bugs.debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: bash X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 10494-bugs@bugs.debian.org id=B10494.94311974231251 (code B ref 10494); Sat, 20 Nov 1999 17:48:33 GMT From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 18:35:19 +0100 (MET) To: 7047@bugs.debian.org, 7047-submitter@bugs.debian.org, 10259@bugs.debian.org, 10259-submitter@bugs.debian.org, 10433@bugs.debian.org, 10433-submitter@bugs.debian.org, 10494@bugs.debian.org, 10494-submitter@bugs.debian.org X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.55379.692952.853369@tango> From Chet Ramey (chet@po.cwru.edu): "The default bash behavior with respect to the exit status of a pipeline will not change. Changing it as suggested in the discussion of #10494 would render bash incompatible with every other shell out there. The behavior of SIGPIPE reporting can be disabled with a compile-time-option (DONT_REPORT_SIGPIPE), settable in config-top.h."   Acknowledgement sent to Matthias Klose <doko@tango.isdn.cs.tu-berlin.de>:
Extra info received and forwarded to list. Copy sent to Guy Maor <maor@debian.org>.   -t  From: owner@bugs.debian.org (Debian Bug Tracking System) To: Matthias Klose Subject: Bug#10494: Info received (was comment from upstream author) Message-ID: In-Reply-To: <14390.55379.692952.853369@tango> References: <14390.55379.692952.853369@tango> X-Debian-PR-Message: ack-info-maintonly 10494 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Guy Maor If you wish to continue to submit further information on your problem, please send it to 10494@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Darren Benham (administrator, Debian Bugs database)   Received: (at 10494) by bugs.debian.org; 20 Nov 1999 17:42:22 +0000 Received: (qmail 31237 invoked from network); 20 Nov 1999 17:42:21 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 17:42:21 -0000 Received: from tango (mail@doko.home.cs.tu-berlin.de [130.149.146.98]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id SAA17693; Sat, 20 Nov 1999 18:35:20 +0100 (MET) Received: from doko by tango with local (Exim 3.03 #1 (Debian)) id 11pEPv-0002RE-00; Sat, 20 Nov 1999 18:35:19 +0100 From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 18:35:19 +0100 (MET) To: 7047@bugs.debian.org, 7047-submitter@bugs.debian.org, 10259@bugs.debian.org, 10259-submitter@bugs.debian.org, 10433@bugs.debian.org, 10433-submitter@bugs.debian.org, 10494@bugs.debian.org, 10494-submitter@bugs.debian.org Subject: comment from upstream author X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.55379.692952.853369@tango> From Chet Ramey (chet@po.cwru.edu): "The default bash behavior with respect to the exit status of a pipeline will not change. Changing it as suggested in the discussion of #10494 would render bash incompatible with every other shell out there. The behavior of SIGPIPE reporting can be disabled with a compile-time-option (DONT_REPORT_SIGPIPE), settable in config-top.h."   Forwarded-to-address changed from bug-bash@prep.ai.mit.edu to chet@po.cwru.edu. Request was from Matthias Klose <doko@tango.isdn.cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 20 Nov 1999 17:39:16 +0000 Received: (qmail 29427 invoked from network); 20 Nov 1999 17:39:16 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 17:39:16 -0000 Received: from tango (mail@doko.home.cs.tu-berlin.de [130.149.146.98]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id SAA17629 for ; Sat, 20 Nov 1999 18:35:00 +0100 (MET) Received: from doko by tango with local (Exim 3.03 #1 (Debian)) id 11pEPb-0002Qm-00; Sat, 20 Nov 1999 18:34:59 +0100 From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 18:34:59 +0100 (MET) To: control@bugs.debian.org Subject: forwarded/fixed bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.56147.346954.484066@tango> # From Chet Ramey: # I looked at all of the bash bug reports on www.debian.org, from # http://www.debian.org/Bugs/db/pa/lbash.html, and tested them against # the about-to-be-open-beta-released bash-2.04. There are some actual # bugs there. The following reports are bugs that I will look at: forwarded 47990 chet@po.cwru.edu # chet: (maybe) forwarded 47179 chet@po.cwru.edu forwarded 36652 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 33900 chet@po.cwru.edu forwarded 30460 chet@po.cwru.edu forwarded 21901 chet@po.cwru.edu forwarded 21363 chet@po.cwru.edu # chet: (maybe -- I can't reproduce it with my vi. I get `no command found'.) forwarded 19211 chet@po.cwru.edu forwarded 15165 chet@po.cwru.edu # From Chet Ramey: # There are new feature requests in the following reports, which I will look # at providing in a future bash version: forwarded 38974 chet@po.cwru.edu forwarded 35975 chet@po.cwru.edu forwarded 14658 chet@po.cwru.edu # From Chet Ramey: # This is a documentation issue: forwarded 42916 chet@po.cwru.edu # forwarded non-bugs forwarded 47849 chet@po.cwru.edu forwarded 45841 chet@po.cwru.edu retitle 45841 [not a bug] builtin cd gives spurious output when envar CDPATH is set severity 45841 fixed forwarded 45379 chet@po.cwru.edu retitle 45379 [not a bug] 'set -e' and subshell interaction severity 45379 fixed merge 45379 35979 forwarded 35979 chet@po.cwru.edu retitle 35979 [not a bug] strange inconsistent behaviour severity 35979 fixed forwarded 38244 chet@po.cwru.edu retitle 38244 [already documented] -v command line option undocumented severity 38244 fixed severity 37971 fixed forwarded 37654 chet@po.cwru.edu retitle 37654 [not a bug] parser makes mistakes when parsing $( and | severity 37654 fixed reassign 36027 general forwarded 35465 chet@po.cwru.edu reassign 33822 locales forwarded 32577 chet@po.cwru.edu forwarded 25245 chet@po.cwru.edu forwarded 22291 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu merge 22291 28789 forwarded 14287 chet@po.cwru.edu forwarded 11938 chet@po.cwru.edu merge 11938 14287 retitle 11938 [fix in bash-2.04] problem with su - foo -c "cmd" / bash-2.0 retitle 14287 [fix in bash-2.04] noninteractive login shell fails to read /etc/profile forwarded 2301 chet@po.cwru.edu forwarded 34833 chet@po.cwru.edu forwarded 36877 chet@po.cwru.edu forwarded 46901 chet@po.cwru.edu forwarded 42916 chet@po.cwru.edu forwarded 44015 chet@po.cwru.edu forwarded 7047 chet@po.cwru.edu forwarded 10259 chet@po.cwru.edu forwarded 10433 chet@po.cwru.edu forwarded 10494 chet@po.cwru.edu forwarded 16797 chet@po.cwru.edu forwarded 29610 chet@po.cwru.edu forwarded 41916 chet@po.cwru.edu forwarded 50353 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu forwarded 27090 chet@po.cwru.edu forwarded 26720 chet@po.cwru.edu forwarded 26619 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 49702 chet@po.cwru.edu forwarded 38411 chet@po.cwru.edu forwarded 37637 chet@po.cwru.edu forwarded 29863 chet@po.cwru.edu forwarded 22517 chet@po.cwru.edu forwarded 16856 chet@po.cwru.edu forwarded 22498 chet@po.cwru.edu forwarded 28849 chet@po.cwru.edu   Forwarded-to-address changed from chet@po.cwru.edu to chet@po.cwru.edu. Request was from Matthias Klose <doko@tango.isdn.cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 20 Nov 1999 17:39:16 +0000 Received: (qmail 29427 invoked from network); 20 Nov 1999 17:39:16 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 17:39:16 -0000 Received: from tango (mail@doko.home.cs.tu-berlin.de [130.149.146.98]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id SAA17629 for ; Sat, 20 Nov 1999 18:35:00 +0100 (MET) Received: from doko by tango with local (Exim 3.03 #1 (Debian)) id 11pEPb-0002Qm-00; Sat, 20 Nov 1999 18:34:59 +0100 From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 18:34:59 +0100 (MET) To: control@bugs.debian.org Subject: forwarded/fixed bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.56147.346954.484066@tango> # From Chet Ramey: # I looked at all of the bash bug reports on www.debian.org, from # http://www.debian.org/Bugs/db/pa/lbash.html, and tested them against # the about-to-be-open-beta-released bash-2.04. There are some actual # bugs there. The following reports are bugs that I will look at: forwarded 47990 chet@po.cwru.edu # chet: (maybe) forwarded 47179 chet@po.cwru.edu forwarded 36652 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 33900 chet@po.cwru.edu forwarded 30460 chet@po.cwru.edu forwarded 21901 chet@po.cwru.edu forwarded 21363 chet@po.cwru.edu # chet: (maybe -- I can't reproduce it with my vi. I get `no command found'.) forwarded 19211 chet@po.cwru.edu forwarded 15165 chet@po.cwru.edu # From Chet Ramey: # There are new feature requests in the following reports, which I will look # at providing in a future bash version: forwarded 38974 chet@po.cwru.edu forwarded 35975 chet@po.cwru.edu forwarded 14658 chet@po.cwru.edu # From Chet Ramey: # This is a documentation issue: forwarded 42916 chet@po.cwru.edu # forwarded non-bugs forwarded 47849 chet@po.cwru.edu forwarded 45841 chet@po.cwru.edu retitle 45841 [not a bug] builtin cd gives spurious output when envar CDPATH is set severity 45841 fixed forwarded 45379 chet@po.cwru.edu retitle 45379 [not a bug] 'set -e' and subshell interaction severity 45379 fixed merge 45379 35979 forwarded 35979 chet@po.cwru.edu retitle 35979 [not a bug] strange inconsistent behaviour severity 35979 fixed forwarded 38244 chet@po.cwru.edu retitle 38244 [already documented] -v command line option undocumented severity 38244 fixed severity 37971 fixed forwarded 37654 chet@po.cwru.edu retitle 37654 [not a bug] parser makes mistakes when parsing $( and | severity 37654 fixed reassign 36027 general forwarded 35465 chet@po.cwru.edu reassign 33822 locales forwarded 32577 chet@po.cwru.edu forwarded 25245 chet@po.cwru.edu forwarded 22291 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu merge 22291 28789 forwarded 14287 chet@po.cwru.edu forwarded 11938 chet@po.cwru.edu merge 11938 14287 retitle 11938 [fix in bash-2.04] problem with su - foo -c "cmd" / bash-2.0 retitle 14287 [fix in bash-2.04] noninteractive login shell fails to read /etc/profile forwarded 2301 chet@po.cwru.edu forwarded 34833 chet@po.cwru.edu forwarded 36877 chet@po.cwru.edu forwarded 46901 chet@po.cwru.edu forwarded 42916 chet@po.cwru.edu forwarded 44015 chet@po.cwru.edu forwarded 7047 chet@po.cwru.edu forwarded 10259 chet@po.cwru.edu forwarded 10433 chet@po.cwru.edu forwarded 10494 chet@po.cwru.edu forwarded 16797 chet@po.cwru.edu forwarded 29610 chet@po.cwru.edu forwarded 41916 chet@po.cwru.edu forwarded 50353 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu forwarded 27090 chet@po.cwru.edu forwarded 26720 chet@po.cwru.edu forwarded 26619 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 49702 chet@po.cwru.edu forwarded 38411 chet@po.cwru.edu forwarded 37637 chet@po.cwru.edu forwarded 29863 chet@po.cwru.edu forwarded 22517 chet@po.cwru.edu forwarded 16856 chet@po.cwru.edu forwarded 22498 chet@po.cwru.edu forwarded 28849 chet@po.cwru.edu   Forwarded-to-address changed from chet@po.cwru.edu to chet@po.cwru.edu. Request was from Matthias Klose <doko@tango.isdn.cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 20 Nov 1999 17:39:16 +0000 Received: (qmail 29427 invoked from network); 20 Nov 1999 17:39:16 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 17:39:16 -0000 Received: from tango (mail@doko.home.cs.tu-berlin.de [130.149.146.98]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id SAA17629 for ; Sat, 20 Nov 1999 18:35:00 +0100 (MET) Received: from doko by tango with local (Exim 3.03 #1 (Debian)) id 11pEPb-0002Qm-00; Sat, 20 Nov 1999 18:34:59 +0100 From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 18:34:59 +0100 (MET) To: control@bugs.debian.org Subject: forwarded/fixed bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.56147.346954.484066@tango> # From Chet Ramey: # I looked at all of the bash bug reports on www.debian.org, from # http://www.debian.org/Bugs/db/pa/lbash.html, and tested them against # the about-to-be-open-beta-released bash-2.04. There are some actual # bugs there. The following reports are bugs that I will look at: forwarded 47990 chet@po.cwru.edu # chet: (maybe) forwarded 47179 chet@po.cwru.edu forwarded 36652 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 33900 chet@po.cwru.edu forwarded 30460 chet@po.cwru.edu forwarded 21901 chet@po.cwru.edu forwarded 21363 chet@po.cwru.edu # chet: (maybe -- I can't reproduce it with my vi. I get `no command found'.) forwarded 19211 chet@po.cwru.edu forwarded 15165 chet@po.cwru.edu # From Chet Ramey: # There are new feature requests in the following reports, which I will look # at providing in a future bash version: forwarded 38974 chet@po.cwru.edu forwarded 35975 chet@po.cwru.edu forwarded 14658 chet@po.cwru.edu # From Chet Ramey: # This is a documentation issue: forwarded 42916 chet@po.cwru.edu # forwarded non-bugs forwarded 47849 chet@po.cwru.edu forwarded 45841 chet@po.cwru.edu retitle 45841 [not a bug] builtin cd gives spurious output when envar CDPATH is set severity 45841 fixed forwarded 45379 chet@po.cwru.edu retitle 45379 [not a bug] 'set -e' and subshell interaction severity 45379 fixed merge 45379 35979 forwarded 35979 chet@po.cwru.edu retitle 35979 [not a bug] strange inconsistent behaviour severity 35979 fixed forwarded 38244 chet@po.cwru.edu retitle 38244 [already documented] -v command line option undocumented severity 38244 fixed severity 37971 fixed forwarded 37654 chet@po.cwru.edu retitle 37654 [not a bug] parser makes mistakes when parsing $( and | severity 37654 fixed reassign 36027 general forwarded 35465 chet@po.cwru.edu reassign 33822 locales forwarded 32577 chet@po.cwru.edu forwarded 25245 chet@po.cwru.edu forwarded 22291 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu merge 22291 28789 forwarded 14287 chet@po.cwru.edu forwarded 11938 chet@po.cwru.edu merge 11938 14287 retitle 11938 [fix in bash-2.04] problem with su - foo -c "cmd" / bash-2.0 retitle 14287 [fix in bash-2.04] noninteractive login shell fails to read /etc/profile forwarded 2301 chet@po.cwru.edu forwarded 34833 chet@po.cwru.edu forwarded 36877 chet@po.cwru.edu forwarded 46901 chet@po.cwru.edu forwarded 42916 chet@po.cwru.edu forwarded 44015 chet@po.cwru.edu forwarded 7047 chet@po.cwru.edu forwarded 10259 chet@po.cwru.edu forwarded 10433 chet@po.cwru.edu forwarded 10494 chet@po.cwru.edu forwarded 16797 chet@po.cwru.edu forwarded 29610 chet@po.cwru.edu forwarded 41916 chet@po.cwru.edu forwarded 50353 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu forwarded 27090 chet@po.cwru.edu forwarded 26720 chet@po.cwru.edu forwarded 26619 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 49702 chet@po.cwru.edu forwarded 38411 chet@po.cwru.edu forwarded 37637 chet@po.cwru.edu forwarded 29863 chet@po.cwru.edu forwarded 22517 chet@po.cwru.edu forwarded 16856 chet@po.cwru.edu forwarded 22498 chet@po.cwru.edu forwarded 28849 chet@po.cwru.edu   Forwarded-to-address changed from chet@po.cwru.edu to chet@po.cwru.edu. Request was from Matthias Klose <doko@tango.isdn.cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 20 Nov 1999 17:39:16 +0000 Received: (qmail 29427 invoked from network); 20 Nov 1999 17:39:16 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 17:39:16 -0000 Received: from tango (mail@doko.home.cs.tu-berlin.de [130.149.146.98]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id SAA17629 for ; Sat, 20 Nov 1999 18:35:00 +0100 (MET) Received: from doko by tango with local (Exim 3.03 #1 (Debian)) id 11pEPb-0002Qm-00; Sat, 20 Nov 1999 18:34:59 +0100 From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 18:34:59 +0100 (MET) To: control@bugs.debian.org Subject: forwarded/fixed bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.56147.346954.484066@tango> # From Chet Ramey: # I looked at all of the bash bug reports on www.debian.org, from # http://www.debian.org/Bugs/db/pa/lbash.html, and tested them against # the about-to-be-open-beta-released bash-2.04. There are some actual # bugs there. The following reports are bugs that I will look at: forwarded 47990 chet@po.cwru.edu # chet: (maybe) forwarded 47179 chet@po.cwru.edu forwarded 36652 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 33900 chet@po.cwru.edu forwarded 30460 chet@po.cwru.edu forwarded 21901 chet@po.cwru.edu forwarded 21363 chet@po.cwru.edu # chet: (maybe -- I can't reproduce it with my vi. I get `no command found'.) forwarded 19211 chet@po.cwru.edu forwarded 15165 chet@po.cwru.edu # From Chet Ramey: # There are new feature requests in the following reports, which I will look # at providing in a future bash version: forwarded 38974 chet@po.cwru.edu forwarded 35975 chet@po.cwru.edu forwarded 14658 chet@po.cwru.edu # From Chet Ramey: # This is a documentation issue: forwarded 42916 chet@po.cwru.edu # forwarded non-bugs forwarded 47849 chet@po.cwru.edu forwarded 45841 chet@po.cwru.edu retitle 45841 [not a bug] builtin cd gives spurious output when envar CDPATH is set severity 45841 fixed forwarded 45379 chet@po.cwru.edu retitle 45379 [not a bug] 'set -e' and subshell interaction severity 45379 fixed merge 45379 35979 forwarded 35979 chet@po.cwru.edu retitle 35979 [not a bug] strange inconsistent behaviour severity 35979 fixed forwarded 38244 chet@po.cwru.edu retitle 38244 [already documented] -v command line option undocumented severity 38244 fixed severity 37971 fixed forwarded 37654 chet@po.cwru.edu retitle 37654 [not a bug] parser makes mistakes when parsing $( and | severity 37654 fixed reassign 36027 general forwarded 35465 chet@po.cwru.edu reassign 33822 locales forwarded 32577 chet@po.cwru.edu forwarded 25245 chet@po.cwru.edu forwarded 22291 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu merge 22291 28789 forwarded 14287 chet@po.cwru.edu forwarded 11938 chet@po.cwru.edu merge 11938 14287 retitle 11938 [fix in bash-2.04] problem with su - foo -c "cmd" / bash-2.0 retitle 14287 [fix in bash-2.04] noninteractive login shell fails to read /etc/profile forwarded 2301 chet@po.cwru.edu forwarded 34833 chet@po.cwru.edu forwarded 36877 chet@po.cwru.edu forwarded 46901 chet@po.cwru.edu forwarded 42916 chet@po.cwru.edu forwarded 44015 chet@po.cwru.edu forwarded 7047 chet@po.cwru.edu forwarded 10259 chet@po.cwru.edu forwarded 10433 chet@po.cwru.edu forwarded 10494 chet@po.cwru.edu forwarded 16797 chet@po.cwru.edu forwarded 29610 chet@po.cwru.edu forwarded 41916 chet@po.cwru.edu forwarded 50353 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu forwarded 27090 chet@po.cwru.edu forwarded 26720 chet@po.cwru.edu forwarded 26619 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 49702 chet@po.cwru.edu forwarded 38411 chet@po.cwru.edu forwarded 37637 chet@po.cwru.edu forwarded 29863 chet@po.cwru.edu forwarded 22517 chet@po.cwru.edu forwarded 16856 chet@po.cwru.edu forwarded 22498 chet@po.cwru.edu forwarded 28849 chet@po.cwru.edu   Message sent on to Miquel van Smoorenburg <miquels@cistron.nl>:
Bug#10494.   Miquel van Smoorenburg  Subject: Bug#10494: comment from upstream author Reply-To: Matthias Klose , 10494-quiet@bugs.debian.org Resent-To: Miquel van Smoorenburg Resent-Date: Sat, 20 Nov 1999 17:49:58 GMT Resent-Message-ID: Resent-Sender: owner@bugs.debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: bash X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 10494-submitter@bugs.debian.org id=U10494.94311974131248 (code U ref 10494); Sat, 20 Nov 1999 17:49:58 GMT From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 18:35:19 +0100 (MET) To: 7047@bugs.debian.org, 7047-submitter@bugs.debian.org, 10259@bugs.debian.org, 10259-submitter@bugs.debian.org, 10433@bugs.debian.org, 10433-submitter@bugs.debian.org, 10494@bugs.debian.org, 10494-submitter@bugs.debian.org X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.55379.692952.853369@tango> From Chet Ramey (chet@po.cwru.edu): "The default bash behavior with respect to the exit status of a pipeline will not change. Changing it as suggested in the discussion of #10494 would render bash incompatible with every other shell out there. The behavior of SIGPIPE reporting can be disabled with a compile-time-option (DONT_REPORT_SIGPIPE), settable in config-top.h."   Received: (at 10494-submitter) by bugs.debian.org; 20 Nov 1999 17:42:21 +0000 Received: (qmail 31237 invoked from network); 20 Nov 1999 17:42:21 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 17:42:21 -0000 Received: from tango (mail@doko.home.cs.tu-berlin.de [130.149.146.98]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id SAA17693; Sat, 20 Nov 1999 18:35:20 +0100 (MET) Received: from doko by tango with local (Exim 3.03 #1 (Debian)) id 11pEPv-0002RE-00; Sat, 20 Nov 1999 18:35:19 +0100 From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 18:35:19 +0100 (MET) To: 7047@bugs.debian.org, 7047-submitter@bugs.debian.org, 10259@bugs.debian.org, 10259-submitter@bugs.debian.org, 10433@bugs.debian.org, 10433-submitter@bugs.debian.org, 10494@bugs.debian.org, 10494-submitter@bugs.debian.org Subject: comment from upstream author X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.55379.692952.853369@tango> From Chet Ramey (chet@po.cwru.edu): "The default bash behavior with respect to the exit status of a pipeline will not change. Changing it as suggested in the discussion of #10494 would render bash incompatible with every other shell out there. The behavior of SIGPIPE reporting can be disabled with a compile-time-option (DONT_REPORT_SIGPIPE), settable in config-top.h."   Forwarded-to-address changed from chet@po.cwru.edu to chet@po.cwru.edu. Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 20 Nov 1999 18:53:54 +0000 Received: (qmail 3374 invoked from network); 20 Nov 1999 18:53:53 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 18:53:53 -0000 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id TAA24837 for ; Sat, 20 Nov 1999 19:50:00 +0100 (MET) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.9.3/8.9.0) id TAA16194; Sat, 20 Nov 1999 19:49:59 +0100 (MET) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 19:49:59 +0100 (MET) To: control@bugs.debian.org Subject: forwarded/fixed bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.60500.916045.893134@bolero> # From Chet Ramey: # I looked at all of the bash bug reports on www.debian.org, from # http://www.debian.org/Bugs/db/pa/lbash.html, and tested them against # the about-to-be-open-beta-released bash-2.04. There are some actual # bugs there. The following reports are bugs that I will look at: forwarded 47990 chet@po.cwru.edu # chet: (maybe) forwarded 47179 chet@po.cwru.edu forwarded 36652 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 33900 chet@po.cwru.edu forwarded 30460 chet@po.cwru.edu forwarded 21901 chet@po.cwru.edu forwarded 21363 chet@po.cwru.edu # chet: (maybe -- I can't reproduce it with my vi. I get `no command found'.) forwarded 19211 chet@po.cwru.edu forwarded 15165 chet@po.cwru.edu # From Chet Ramey: # There are new feature requests in the following reports, which I will look # at providing in a future bash version: forwarded 38974 chet@po.cwru.edu forwarded 35975 chet@po.cwru.edu forwarded 14658 chet@po.cwru.edu # From Chet Ramey: # This is a documentation issue: forwarded 42916 chet@po.cwru.edu retitle 50153 [not a bug] some prompts (PS1) destroy scrolling severity 50153 fixed # forwarded non-bugs forwarded 47849 chet@po.cwru.edu forwarded 45841 chet@po.cwru.edu retitle 45841 [not a bug] builtin cd gives spurious output when envar CDPATH is set severity 45841 fixed forwarded 45379 chet@po.cwru.edu retitle 45379 [not a bug] 'set -e' and subshell interaction severity 45379 fixed merge 45379 35979 forwarded 35979 chet@po.cwru.edu retitle 35979 [not a bug] strange inconsistent behaviour severity 35979 fixed forwarded 38244 chet@po.cwru.edu retitle 38244 [already documented] -v command line option undocumented severity 38244 fixed severity 37971 fixed forwarded 37654 chet@po.cwru.edu retitle 37654 [not a bug] parser makes mistakes when parsing $( and | severity 37654 fixed reassign 36027 general forwarded 35465 chet@po.cwru.edu reassign 33822 locales forwarded 32577 chet@po.cwru.edu forwarded 25245 chet@po.cwru.edu forwarded 22291 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu merge 22291 28789 forwarded 14287 chet@po.cwru.edu forwarded 11938 chet@po.cwru.edu merge 11938 14287 retitle 11938 [fix in bash-2.04] problem with su - foo -c "cmd" / bash-2.0 retitle 14287 [fix in bash-2.04] noninteractive login shell fails to read /etc/profile forwarded 2301 chet@po.cwru.edu forwarded 34833 chet@po.cwru.edu forwarded 36877 chet@po.cwru.edu forwarded 46901 chet@po.cwru.edu forwarded 42916 chet@po.cwru.edu forwarded 44015 chet@po.cwru.edu forwarded 7047 chet@po.cwru.edu forwarded 10259 chet@po.cwru.edu forwarded 10433 chet@po.cwru.edu forwarded 10494 chet@po.cwru.edu forwarded 16797 chet@po.cwru.edu forwarded 29610 chet@po.cwru.edu forwarded 41916 chet@po.cwru.edu forwarded 50353 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu forwarded 27090 chet@po.cwru.edu forwarded 26720 chet@po.cwru.edu forwarded 26619 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 49702 chet@po.cwru.edu forwarded 38411 chet@po.cwru.edu forwarded 37637 chet@po.cwru.edu forwarded 29863 chet@po.cwru.edu forwarded 22517 chet@po.cwru.edu forwarded 16856 chet@po.cwru.edu forwarded 22498 chet@po.cwru.edu forwarded 28849 chet@po.cwru.edu thanks   Forwarded-to-address changed from chet@po.cwru.edu to chet@po.cwru.edu. Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 20 Nov 1999 18:53:54 +0000 Received: (qmail 3374 invoked from network); 20 Nov 1999 18:53:53 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 18:53:53 -0000 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id TAA24837 for ; Sat, 20 Nov 1999 19:50:00 +0100 (MET) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.9.3/8.9.0) id TAA16194; Sat, 20 Nov 1999 19:49:59 +0100 (MET) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 19:49:59 +0100 (MET) To: control@bugs.debian.org Subject: forwarded/fixed bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.60500.916045.893134@bolero> # From Chet Ramey: # I looked at all of the bash bug reports on www.debian.org, from # http://www.debian.org/Bugs/db/pa/lbash.html, and tested them against # the about-to-be-open-beta-released bash-2.04. There are some actual # bugs there. The following reports are bugs that I will look at: forwarded 47990 chet@po.cwru.edu # chet: (maybe) forwarded 47179 chet@po.cwru.edu forwarded 36652 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 33900 chet@po.cwru.edu forwarded 30460 chet@po.cwru.edu forwarded 21901 chet@po.cwru.edu forwarded 21363 chet@po.cwru.edu # chet: (maybe -- I can't reproduce it with my vi. I get `no command found'.) forwarded 19211 chet@po.cwru.edu forwarded 15165 chet@po.cwru.edu # From Chet Ramey: # There are new feature requests in the following reports, which I will look # at providing in a future bash version: forwarded 38974 chet@po.cwru.edu forwarded 35975 chet@po.cwru.edu forwarded 14658 chet@po.cwru.edu # From Chet Ramey: # This is a documentation issue: forwarded 42916 chet@po.cwru.edu retitle 50153 [not a bug] some prompts (PS1) destroy scrolling severity 50153 fixed # forwarded non-bugs forwarded 47849 chet@po.cwru.edu forwarded 45841 chet@po.cwru.edu retitle 45841 [not a bug] builtin cd gives spurious output when envar CDPATH is set severity 45841 fixed forwarded 45379 chet@po.cwru.edu retitle 45379 [not a bug] 'set -e' and subshell interaction severity 45379 fixed merge 45379 35979 forwarded 35979 chet@po.cwru.edu retitle 35979 [not a bug] strange inconsistent behaviour severity 35979 fixed forwarded 38244 chet@po.cwru.edu retitle 38244 [already documented] -v command line option undocumented severity 38244 fixed severity 37971 fixed forwarded 37654 chet@po.cwru.edu retitle 37654 [not a bug] parser makes mistakes when parsing $( and | severity 37654 fixed reassign 36027 general forwarded 35465 chet@po.cwru.edu reassign 33822 locales forwarded 32577 chet@po.cwru.edu forwarded 25245 chet@po.cwru.edu forwarded 22291 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu merge 22291 28789 forwarded 14287 chet@po.cwru.edu forwarded 11938 chet@po.cwru.edu merge 11938 14287 retitle 11938 [fix in bash-2.04] problem with su - foo -c "cmd" / bash-2.0 retitle 14287 [fix in bash-2.04] noninteractive login shell fails to read /etc/profile forwarded 2301 chet@po.cwru.edu forwarded 34833 chet@po.cwru.edu forwarded 36877 chet@po.cwru.edu forwarded 46901 chet@po.cwru.edu forwarded 42916 chet@po.cwru.edu forwarded 44015 chet@po.cwru.edu forwarded 7047 chet@po.cwru.edu forwarded 10259 chet@po.cwru.edu forwarded 10433 chet@po.cwru.edu forwarded 10494 chet@po.cwru.edu forwarded 16797 chet@po.cwru.edu forwarded 29610 chet@po.cwru.edu forwarded 41916 chet@po.cwru.edu forwarded 50353 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu forwarded 27090 chet@po.cwru.edu forwarded 26720 chet@po.cwru.edu forwarded 26619 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 49702 chet@po.cwru.edu forwarded 38411 chet@po.cwru.edu forwarded 37637 chet@po.cwru.edu forwarded 29863 chet@po.cwru.edu forwarded 22517 chet@po.cwru.edu forwarded 16856 chet@po.cwru.edu forwarded 22498 chet@po.cwru.edu forwarded 28849 chet@po.cwru.edu thanks   Forwarded-to-address changed from chet@po.cwru.edu to chet@po.cwru.edu. Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 20 Nov 1999 18:53:54 +0000 Received: (qmail 3374 invoked from network); 20 Nov 1999 18:53:53 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 18:53:53 -0000 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id TAA24837 for ; Sat, 20 Nov 1999 19:50:00 +0100 (MET) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.9.3/8.9.0) id TAA16194; Sat, 20 Nov 1999 19:49:59 +0100 (MET) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 19:49:59 +0100 (MET) To: control@bugs.debian.org Subject: forwarded/fixed bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.60500.916045.893134@bolero> # From Chet Ramey: # I looked at all of the bash bug reports on www.debian.org, from # http://www.debian.org/Bugs/db/pa/lbash.html, and tested them against # the about-to-be-open-beta-released bash-2.04. There are some actual # bugs there. The following reports are bugs that I will look at: forwarded 47990 chet@po.cwru.edu # chet: (maybe) forwarded 47179 chet@po.cwru.edu forwarded 36652 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 33900 chet@po.cwru.edu forwarded 30460 chet@po.cwru.edu forwarded 21901 chet@po.cwru.edu forwarded 21363 chet@po.cwru.edu # chet: (maybe -- I can't reproduce it with my vi. I get `no command found'.) forwarded 19211 chet@po.cwru.edu forwarded 15165 chet@po.cwru.edu # From Chet Ramey: # There are new feature requests in the following reports, which I will look # at providing in a future bash version: forwarded 38974 chet@po.cwru.edu forwarded 35975 chet@po.cwru.edu forwarded 14658 chet@po.cwru.edu # From Chet Ramey: # This is a documentation issue: forwarded 42916 chet@po.cwru.edu retitle 50153 [not a bug] some prompts (PS1) destroy scrolling severity 50153 fixed # forwarded non-bugs forwarded 47849 chet@po.cwru.edu forwarded 45841 chet@po.cwru.edu retitle 45841 [not a bug] builtin cd gives spurious output when envar CDPATH is set severity 45841 fixed forwarded 45379 chet@po.cwru.edu retitle 45379 [not a bug] 'set -e' and subshell interaction severity 45379 fixed merge 45379 35979 forwarded 35979 chet@po.cwru.edu retitle 35979 [not a bug] strange inconsistent behaviour severity 35979 fixed forwarded 38244 chet@po.cwru.edu retitle 38244 [already documented] -v command line option undocumented severity 38244 fixed severity 37971 fixed forwarded 37654 chet@po.cwru.edu retitle 37654 [not a bug] parser makes mistakes when parsing $( and | severity 37654 fixed reassign 36027 general forwarded 35465 chet@po.cwru.edu reassign 33822 locales forwarded 32577 chet@po.cwru.edu forwarded 25245 chet@po.cwru.edu forwarded 22291 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu merge 22291 28789 forwarded 14287 chet@po.cwru.edu forwarded 11938 chet@po.cwru.edu merge 11938 14287 retitle 11938 [fix in bash-2.04] problem with su - foo -c "cmd" / bash-2.0 retitle 14287 [fix in bash-2.04] noninteractive login shell fails to read /etc/profile forwarded 2301 chet@po.cwru.edu forwarded 34833 chet@po.cwru.edu forwarded 36877 chet@po.cwru.edu forwarded 46901 chet@po.cwru.edu forwarded 42916 chet@po.cwru.edu forwarded 44015 chet@po.cwru.edu forwarded 7047 chet@po.cwru.edu forwarded 10259 chet@po.cwru.edu forwarded 10433 chet@po.cwru.edu forwarded 10494 chet@po.cwru.edu forwarded 16797 chet@po.cwru.edu forwarded 29610 chet@po.cwru.edu forwarded 41916 chet@po.cwru.edu forwarded 50353 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu forwarded 27090 chet@po.cwru.edu forwarded 26720 chet@po.cwru.edu forwarded 26619 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 49702 chet@po.cwru.edu forwarded 38411 chet@po.cwru.edu forwarded 37637 chet@po.cwru.edu forwarded 29863 chet@po.cwru.edu forwarded 22517 chet@po.cwru.edu forwarded 16856 chet@po.cwru.edu forwarded 22498 chet@po.cwru.edu forwarded 28849 chet@po.cwru.edu thanks   Forwarded-to-address changed from chet@po.cwru.edu to chet@po.cwru.edu. Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 20 Nov 1999 18:53:54 +0000 Received: (qmail 3374 invoked from network); 20 Nov 1999 18:53:53 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 20 Nov 1999 18:53:53 -0000 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id TAA24837 for ; Sat, 20 Nov 1999 19:50:00 +0100 (MET) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.9.3/8.9.0) id TAA16194; Sat, 20 Nov 1999 19:49:59 +0100 (MET) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 20 Nov 1999 19:49:59 +0100 (MET) To: control@bugs.debian.org Subject: forwarded/fixed bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14390.60500.916045.893134@bolero> # From Chet Ramey: # I looked at all of the bash bug reports on www.debian.org, from # http://www.debian.org/Bugs/db/pa/lbash.html, and tested them against # the about-to-be-open-beta-released bash-2.04. There are some actual # bugs there. The following reports are bugs that I will look at: forwarded 47990 chet@po.cwru.edu # chet: (maybe) forwarded 47179 chet@po.cwru.edu forwarded 36652 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 33900 chet@po.cwru.edu forwarded 30460 chet@po.cwru.edu forwarded 21901 chet@po.cwru.edu forwarded 21363 chet@po.cwru.edu # chet: (maybe -- I can't reproduce it with my vi. I get `no command found'.) forwarded 19211 chet@po.cwru.edu forwarded 15165 chet@po.cwru.edu # From Chet Ramey: # There are new feature requests in the following reports, which I will look # at providing in a future bash version: forwarded 38974 chet@po.cwru.edu forwarded 35975 chet@po.cwru.edu forwarded 14658 chet@po.cwru.edu # From Chet Ramey: # This is a documentation issue: forwarded 42916 chet@po.cwru.edu retitle 50153 [not a bug] some prompts (PS1) destroy scrolling severity 50153 fixed # forwarded non-bugs forwarded 47849 chet@po.cwru.edu forwarded 45841 chet@po.cwru.edu retitle 45841 [not a bug] builtin cd gives spurious output when envar CDPATH is set severity 45841 fixed forwarded 45379 chet@po.cwru.edu retitle 45379 [not a bug] 'set -e' and subshell interaction severity 45379 fixed merge 45379 35979 forwarded 35979 chet@po.cwru.edu retitle 35979 [not a bug] strange inconsistent behaviour severity 35979 fixed forwarded 38244 chet@po.cwru.edu retitle 38244 [already documented] -v command line option undocumented severity 38244 fixed severity 37971 fixed forwarded 37654 chet@po.cwru.edu retitle 37654 [not a bug] parser makes mistakes when parsing $( and | severity 37654 fixed reassign 36027 general forwarded 35465 chet@po.cwru.edu reassign 33822 locales forwarded 32577 chet@po.cwru.edu forwarded 25245 chet@po.cwru.edu forwarded 22291 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu merge 22291 28789 forwarded 14287 chet@po.cwru.edu forwarded 11938 chet@po.cwru.edu merge 11938 14287 retitle 11938 [fix in bash-2.04] problem with su - foo -c "cmd" / bash-2.0 retitle 14287 [fix in bash-2.04] noninteractive login shell fails to read /etc/profile forwarded 2301 chet@po.cwru.edu forwarded 34833 chet@po.cwru.edu forwarded 36877 chet@po.cwru.edu forwarded 46901 chet@po.cwru.edu forwarded 42916 chet@po.cwru.edu forwarded 44015 chet@po.cwru.edu forwarded 7047 chet@po.cwru.edu forwarded 10259 chet@po.cwru.edu forwarded 10433 chet@po.cwru.edu forwarded 10494 chet@po.cwru.edu forwarded 16797 chet@po.cwru.edu forwarded 29610 chet@po.cwru.edu forwarded 41916 chet@po.cwru.edu forwarded 50353 chet@po.cwru.edu forwarded 28789 chet@po.cwru.edu forwarded 27090 chet@po.cwru.edu forwarded 26720 chet@po.cwru.edu forwarded 26619 chet@po.cwru.edu forwarded 35127 chet@po.cwru.edu forwarded 49702 chet@po.cwru.edu forwarded 38411 chet@po.cwru.edu forwarded 37637 chet@po.cwru.edu forwarded 29863 chet@po.cwru.edu forwarded 22517 chet@po.cwru.edu forwarded 16856 chet@po.cwru.edu forwarded 22498 chet@po.cwru.edu forwarded 28849 chet@po.cwru.edu thanks   Information forwarded to Guy Maor <maor@debian.org>:
Bug#10494; Package bash.   Guy Maor  Subject: Bug#10494: answer to forwarded bash bug Reply-To: Matthias Klose , 10494-maintonly@bugs.debian.org Resent-From: Matthias Klose Resent-To: Guy Maor Resent-Date: Mon, 22 Nov 1999 09:18:06 GMT Resent-Message-ID: Resent-Sender: owner@bugs.debian.org X-Debian-PR-Message: report 10494 X-Debian-PR-Package: bash X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 10494-maintonly@bugs.debian.org id=M10494.94326224210186 (code M ref 10494); Mon, 22 Nov 1999 09:18:06 GMT From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 22 Nov 1999 09:44:08 +0100 (MET) To: 7047-maintonly@bugs.debian.org, 7047-submitter@bugs.debian.org, 10259-maintonly@bugs.debian.org, 10259-submitter@bugs.debian.org, 10433-maintonly@bugs.debian.org, 10433-submitter@bugs.debian.org, 10494-maintonly@bugs.debian.org, -10494submitter@bugs.debian.org X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14393.480.343679.722015@bolero> This bug was commented by the upstream author Chet Ramey : "The default bash behavior with respect to the exit status of a pipeline will not change. Changing it as suggested in the discussion of #10494 would render bash incompatible with every other shell out there. The behavior of SIGPIPE reporting can be disabled with a compile-time-option (DONT_REPORT_SIGPIPE), settable in config-top.h."   Acknowledgement sent to Matthias Klose <doko@cs.tu-berlin.de>:
Extra info received and forwarded to maintainer. Copy sent to Guy Maor <maor@debian.org>.   -t  From: owner@bugs.debian.org (Debian Bug Tracking System) To: Matthias Klose Subject: Bug#10494: Info received for maintainer only (was answer to forwarded bash bug) Message-ID: In-Reply-To: <14393.480.343679.722015@bolero> References: <14393.480.343679.722015@bolero> X-Debian-PR-Message: ack-info 10494 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) (but not to the mailing list) to accompany the original report. Your message has been sent to the package maintainer(s): Guy Maor If you wish to continue to submit further information on your problem, please send it to 10494-maintonly@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Darren Benham (administrator, Debian Bugs database)   Received: (at 10494-maintonly) by bugs.debian.org; 22 Nov 1999 09:17:22 +0000 Received: (qmail 10172 invoked from network); 22 Nov 1999 09:17:21 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 22 Nov 1999 09:17:21 -0000 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id JAA28878; Mon, 22 Nov 1999 09:44:10 +0100 (MET) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.9.3/8.9.0) id JAA08024; Mon, 22 Nov 1999 09:44:09 +0100 (MET) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 22 Nov 1999 09:44:08 +0100 (MET) To: 7047-maintonly@bugs.debian.org, 7047-submitter@bugs.debian.org, 10259-maintonly@bugs.debian.org, 10259-submitter@bugs.debian.org, 10433-maintonly@bugs.debian.org, 10433-submitter@bugs.debian.org, 10494-maintonly@bugs.debian.org, -10494submitter@bugs.debian.org Subject: answer to forwarded bash bug X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14393.480.343679.722015@bolero> This bug was commented by the upstream author Chet Ramey : "The default bash behavior with respect to the exit status of a pipeline will not change. Changing it as suggested in the discussion of #10494 would render bash incompatible with every other shell out there. The behavior of SIGPIPE reporting can be disabled with a compile-time-option (DONT_REPORT_SIGPIPE), settable in config-top.h."   Changed Bug title. Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 21 Dec 1999 18:04:10 +0000 Received: (qmail 1170 invoked from network); 21 Dec 1999 18:04:09 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 21 Dec 1999 18:04:09 -0000 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.1) with ESMTP id TAA12416 for ; Tue, 21 Dec 1999 19:03:07 +0100 (MET) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.9.3/8.9.3) id TAA25242; Tue, 21 Dec 1999 19:03:06 +0100 (MET) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 21 Dec 1999 19:03:05 +0100 (MET) To: control@bugs.debian.org Subject: retitleing bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14431.48705.625327.431205@bolero> retitle 36877 [commented upstream] should check $PATH if hash fails retitle 10259 [behaviour will not change] exit status of a pipe retitle 10433 [behaviour will not change] exit status of a pipe retitle 10494 [behaviour will not change] exit status of a pipe retitle 42916 [in evaluation] bash-builtins: man getopts incompletely describes optstring thanks   Disconnected #10259 from all other report(s). Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 23 Feb 2000 00:32:33 +0000 Received: (qmail 19969 invoked from network); 23 Feb 2000 00:32:32 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 23 Feb 2000 00:32:32 -0000 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id BAA05269 for ; Wed, 23 Feb 2000 01:31:57 +0100 (MET) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.9.3/8.9.3) id BAA09730; Wed, 23 Feb 2000 01:31:56 +0100 (MET) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 23 Feb 2000 01:31:55 +0100 (MET) To: control@bugs.debian.org Subject: unmerging bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14515.10810.713818.754049@bolero> unmerge 10259 unmerge 10433 thanks   Disconnected #10433 from all other report(s). Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 23 Feb 2000 00:32:33 +0000 Received: (qmail 19969 invoked from network); 23 Feb 2000 00:32:32 -0000 Received: from mail.cs.tu-berlin.de (root@130.149.17.13) by master.debian.org with SMTP; 23 Feb 2000 00:32:32 -0000 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id BAA05269 for ; Wed, 23 Feb 2000 01:31:57 +0100 (MET) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.9.3/8.9.3) id BAA09730; Wed, 23 Feb 2000 01:31:56 +0100 (MET) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 23 Feb 2000 01:31:55 +0100 (MET) To: control@bugs.debian.org Subject: unmerging bash bugs X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14515.10810.713818.754049@bolero> unmerge 10259 unmerge 10433 thanks   Tags added: upstream Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 10 Oct 2003 22:59:13 +0000 From doko@cs.tu-berlin.de Fri Oct 10 17:59:12 2003 Return-path: Received: from mail.cs.tu-berlin.de [130.149.17.13] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1A86E3-0007CY-00; Fri, 10 Oct 2003 17:59:11 -0500 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id AAA27014 for ; Sat, 11 Oct 2003 00:55:25 +0200 (MET DST) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id h9AMtPj2000913; Sat, 11 Oct 2003 00:55:25 +0200 (MEST) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16263.14557.571565.287067@gargle.gargle.HOWL> Date: Sat, 11 Oct 2003 00:55:25 +0200 To: control@bugs.debian.org Subject: tagging readline and bash reports fixed upstream X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid Delivered-To: control@bugs.debian.org X-Spam-Status: No, hits=0.0 required=4.0 tests=none version=2.53-bugs.debian.org_2003_10_09 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_10_09 (1.174.2.15-2003-03-30-exp) retitle 179883 [fixed in 5.0] prompt overwriting with multibyte locale support tags 179883 + upstream tags 179883 + fixed-upstream retitle 172849 [fixed in 5.0] bug in the callback read-char interface tags 172849 + upstream tags 172849 + fixed-upstream tags 173659 + upstream tags 195678 + upstream tags 200871 + patch retitle 154063 [fixed in 5.0] readline redraws entire line for every key tags 154063 + fixed-upstream retitle 154884 [fixed in 5.0] input becomes extremely slow with long lines in MBCS tags 154884 + fixed-upstream tags 153974 + fixed-upstream tags 144585 + upstream tags 115500 + upstream retitle 65484 [fixed in 5.0] readline: namespace pollution tags 65484 + fixed-upstream tags 65484 + upstream tags 64203 + upstream tags 64203 + moreinfo tags 64203 + unreproducible tags 161057 + upstream tags 141292 + upstream tags 140914 + upstream tags 140914 + unreproducible tags 120910 + upstream tags 50853 + upstream tags 168331 + fixed-upstream retitle 168331 [fixed in 3.0] value of various assignments not documented tags 21645 + upstream tags 165533 + upstream tags 165533 + fixed-upstream retitle 165533 [fixed in 3.0] bash: PS4='``' bash -xc : segfaults tags 158035 + upstream tags 162952 + upstream tags 164134 + upstream tags 211426 + fixed-upstream retitle 211426 [fixed in 3.0] bash: stats maildir even though MAILCHECK=-1 tags 186218 + fixed-upstream tags 180290 + fixed-upstream tags 174744 + fixed-upstream tags 168321 + fixed-upstream tags 167003 + upstream tags 167003 + fixed-upstream retitle 167003 [fixed in 3.0] "read -a foo <<< $(echo)" segfaults tags 167002 + fixed-upstream retitle 167002 [fixed in 3.0] indirection not working with arrays tags 165212 + upstream tags 165212 + fixed-upstream retitle 165212 [fixed in 3.0] history substitution: !* can't handle <(foo) tags 164134 + upstream tags 164134 + fixed-upstream retitle 164134 [fixed in 3.0] bash: EINTR kills redirection tags 162952 + fixed-upstream retitle 162952 [fixed in 3.0] infinite loop with IFS="" and compgen -W tags 152847 + upstream tags 152847 + fixed-upstream retitle 152847 [fixed in 3.0] bash: auto-logout doesn't run .logout tags 120340 + upstream tags 7047 + upstream tags 7047 + wontfix tags 10494 + upstream tags 10494 + wontfix tags 61739 + upstream tags 62517 + upstream tags 72520 + upstream tags 86397 + upstream tags 90611 + upstream tags 110969 + upstream tags 159771 + upstream forwarded 159771 chet@po.cwru.edu merge 120340 159771 tags 186165 + upstream forwarded 186165 chet@po.cwru.edu forwarded 177517 chet@po.cwru.edu forwarded 175796 chet@po.cwru.edu forwarded 173982 chet@po.cwru.edu forwarded 173816 chet@po.cwru.edu forwarded 168701 chet@po.cwru.edu tags 168701 + upstream merge 116082 128997 tags 197965 + upstream tags 197965 + fixed-upstream retitle 193570 [fixed in 3.0] kill doesn't differenciate non-numbers tags 193570 + upstream tags 193570 + fixed-upstream forwarded 186994 chet@po.cwru.edu tags 186994 + upstream tags 186994 + fixed-upstream forwarded 176968 chet@po.cwru.edu tags 176968 + fixed-upstream retitle 176968 [fixed in 3.0] bash: printf abc output dissappears under bash prompt tags 174133 + fixed-upstream retitle 174133 [fixed in 3.0] bash: wait: not the child of this shell: not properly documented tags 168318 + upstream tags 168318 + fixed-upstream retitle 168318 [fixed in 3.0] bash: ${!PREFIX@} expansion not documented tags 168267 + upstream tags 168267 + fixed-upstream tags 155369 + upstream forwarded 111467 chet@po.cwru.edu severity 100743 minor forwarded 199042 chet@po.cwru.edu severity 199042 minor merge 100743 111467 merge 100743 199042 retitle 211693 [fixed in 3.0] bash -c 'segfaulting-command ; echo yes' doesn't report the segfault tags 211693 + upstream tags 211693 + fixed-upstream forwarded 204766 chet@po.cwru.edu tags 204766 + upstream forwarded 203767 chet@po.cwru.edu tags 203767 + upstream forwarded 199703 chet@po.cwru.edu tags 199703 + upstream tags 197440 + unreproducible retitle 195116 [fixed in 3.0] ferror called w/o always first calling clearerr results in spurious errors reported tags 195116 + upstream tags 195116 + fixed-upstream forwarded 192831 chet@po.cwru.edu tags 192831 + upstream merge 192831 203767 tags 187727 + upstream forwarded 187727 chet@po.cwru.edu tags 183352 + upstream tags 183352 + fixed-upstream retitle 183352 [fixed in 3.0] fix documentation about exit status of unset builtin forwarded 180075 chet@po.cwru.edu tags 180075 + upstream merge 190028 180075 tags 178828 + fixed-upstream retitle 178828 [fixed in 3.0] Missing trailing slash when completing directory names tags 173744 + fixed-upstream retitle 173744 [fixed in 3.0] bash: $((++)) updates differently for non built-in forwarded 173588 chet@po.cwru.edu tags 173148 + upstream tags 173148 + fixed-upstream retitle 173148 [fixed in 3.0] bash: <$var uses new value of var, contrary to POSIX forwarded 173022 chet@po.cwru.edu tags 172971 + upstream tags 172971 + fixed-upstream retitle 172971 [fixed in 3.0] syntax parsing error involving ; tags 170298 + upstream tags 170298 + fixed-upstream retitle 170298 [fixed in 3.0] rbash is broken as login shell retitle 162773 [fixed in 3.0] segfault when sourcing file tags 162773 - moreinfo tags 162773 - unreproducible tags 162773 + upstream tags 162773 + fixed-upstream tags 160932 + unreproducible tags 157954 + upstream tags 157954 + fixed-upstream retitle 157954 [fixed in 3.0] bash: literal dollars interfere with brace expansion forwarded 155134 chet@po.cwru.edu tags 155134 + upstream tags 155134 + fixed-upstream retitle 155134 [fixed in 3.0] errors in completion of executable's name forwarded 131101 ian@caliban.org tags 189006 + upstream tags 189006 + fixed-upstream retitle 189006 [fixed in 3.0] bash: tab completion on relative path directories thanks   Tags added: wontfix Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 10 Oct 2003 22:59:13 +0000 From doko@cs.tu-berlin.de Fri Oct 10 17:59:12 2003 Return-path: Received: from mail.cs.tu-berlin.de [130.149.17.13] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1A86E3-0007CY-00; Fri, 10 Oct 2003 17:59:11 -0500 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id AAA27014 for ; Sat, 11 Oct 2003 00:55:25 +0200 (MET DST) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id h9AMtPj2000913; Sat, 11 Oct 2003 00:55:25 +0200 (MEST) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16263.14557.571565.287067@gargle.gargle.HOWL> Date: Sat, 11 Oct 2003 00:55:25 +0200 To: control@bugs.debian.org Subject: tagging readline and bash reports fixed upstream X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid Delivered-To: control@bugs.debian.org X-Spam-Status: No, hits=0.0 required=4.0 tests=none version=2.53-bugs.debian.org_2003_10_09 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_10_09 (1.174.2.15-2003-03-30-exp) retitle 179883 [fixed in 5.0] prompt overwriting with multibyte locale support tags 179883 + upstream tags 179883 + fixed-upstream retitle 172849 [fixed in 5.0] bug in the callback read-char interface tags 172849 + upstream tags 172849 + fixed-upstream tags 173659 + upstream tags 195678 + upstream tags 200871 + patch retitle 154063 [fixed in 5.0] readline redraws entire line for every key tags 154063 + fixed-upstream retitle 154884 [fixed in 5.0] input becomes extremely slow with long lines in MBCS tags 154884 + fixed-upstream tags 153974 + fixed-upstream tags 144585 + upstream tags 115500 + upstream retitle 65484 [fixed in 5.0] readline: namespace pollution tags 65484 + fixed-upstream tags 65484 + upstream tags 64203 + upstream tags 64203 + moreinfo tags 64203 + unreproducible tags 161057 + upstream tags 141292 + upstream tags 140914 + upstream tags 140914 + unreproducible tags 120910 + upstream tags 50853 + upstream tags 168331 + fixed-upstream retitle 168331 [fixed in 3.0] value of various assignments not documented tags 21645 + upstream tags 165533 + upstream tags 165533 + fixed-upstream retitle 165533 [fixed in 3.0] bash: PS4='``' bash -xc : segfaults tags 158035 + upstream tags 162952 + upstream tags 164134 + upstream tags 211426 + fixed-upstream retitle 211426 [fixed in 3.0] bash: stats maildir even though MAILCHECK=-1 tags 186218 + fixed-upstream tags 180290 + fixed-upstream tags 174744 + fixed-upstream tags 168321 + fixed-upstream tags 167003 + upstream tags 167003 + fixed-upstream retitle 167003 [fixed in 3.0] "read -a foo <<< $(echo)" segfaults tags 167002 + fixed-upstream retitle 167002 [fixed in 3.0] indirection not working with arrays tags 165212 + upstream tags 165212 + fixed-upstream retitle 165212 [fixed in 3.0] history substitution: !* can't handle <(foo) tags 164134 + upstream tags 164134 + fixed-upstream retitle 164134 [fixed in 3.0] bash: EINTR kills redirection tags 162952 + fixed-upstream retitle 162952 [fixed in 3.0] infinite loop with IFS="" and compgen -W tags 152847 + upstream tags 152847 + fixed-upstream retitle 152847 [fixed in 3.0] bash: auto-logout doesn't run .logout tags 120340 + upstream tags 7047 + upstream tags 7047 + wontfix tags 10494 + upstream tags 10494 + wontfix tags 61739 + upstream tags 62517 + upstream tags 72520 + upstream tags 86397 + upstream tags 90611 + upstream tags 110969 + upstream tags 159771 + upstream forwarded 159771 chet@po.cwru.edu merge 120340 159771 tags 186165 + upstream forwarded 186165 chet@po.cwru.edu forwarded 177517 chet@po.cwru.edu forwarded 175796 chet@po.cwru.edu forwarded 173982 chet@po.cwru.edu forwarded 173816 chet@po.cwru.edu forwarded 168701 chet@po.cwru.edu tags 168701 + upstream merge 116082 128997 tags 197965 + upstream tags 197965 + fixed-upstream retitle 193570 [fixed in 3.0] kill doesn't differenciate non-numbers tags 193570 + upstream tags 193570 + fixed-upstream forwarded 186994 chet@po.cwru.edu tags 186994 + upstream tags 186994 + fixed-upstream forwarded 176968 chet@po.cwru.edu tags 176968 + fixed-upstream retitle 176968 [fixed in 3.0] bash: printf abc output dissappears under bash prompt tags 174133 + fixed-upstream retitle 174133 [fixed in 3.0] bash: wait: not the child of this shell: not properly documented tags 168318 + upstream tags 168318 + fixed-upstream retitle 168318 [fixed in 3.0] bash: ${!PREFIX@} expansion not documented tags 168267 + upstream tags 168267 + fixed-upstream tags 155369 + upstream forwarded 111467 chet@po.cwru.edu severity 100743 minor forwarded 199042 chet@po.cwru.edu severity 199042 minor merge 100743 111467 merge 100743 199042 retitle 211693 [fixed in 3.0] bash -c 'segfaulting-command ; echo yes' doesn't report the segfault tags 211693 + upstream tags 211693 + fixed-upstream forwarded 204766 chet@po.cwru.edu tags 204766 + upstream forwarded 203767 chet@po.cwru.edu tags 203767 + upstream forwarded 199703 chet@po.cwru.edu tags 199703 + upstream tags 197440 + unreproducible retitle 195116 [fixed in 3.0] ferror called w/o always first calling clearerr results in spurious errors reported tags 195116 + upstream tags 195116 + fixed-upstream forwarded 192831 chet@po.cwru.edu tags 192831 + upstream merge 192831 203767 tags 187727 + upstream forwarded 187727 chet@po.cwru.edu tags 183352 + upstream tags 183352 + fixed-upstream retitle 183352 [fixed in 3.0] fix documentation about exit status of unset builtin forwarded 180075 chet@po.cwru.edu tags 180075 + upstream merge 190028 180075 tags 178828 + fixed-upstream retitle 178828 [fixed in 3.0] Missing trailing slash when completing directory names tags 173744 + fixed-upstream retitle 173744 [fixed in 3.0] bash: $((++)) updates differently for non built-in forwarded 173588 chet@po.cwru.edu tags 173148 + upstream tags 173148 + fixed-upstream retitle 173148 [fixed in 3.0] bash: <$var uses new value of var, contrary to POSIX forwarded 173022 chet@po.cwru.edu tags 172971 + upstream tags 172971 + fixed-upstream retitle 172971 [fixed in 3.0] syntax parsing error involving ; tags 170298 + upstream tags 170298 + fixed-upstream retitle 170298 [fixed in 3.0] rbash is broken as login shell retitle 162773 [fixed in 3.0] segfault when sourcing file tags 162773 - moreinfo tags 162773 - unreproducible tags 162773 + upstream tags 162773 + fixed-upstream tags 160932 + unreproducible tags 157954 + upstream tags 157954 + fixed-upstream retitle 157954 [fixed in 3.0] bash: literal dollars interfere with brace expansion forwarded 155134 chet@po.cwru.edu tags 155134 + upstream tags 155134 + fixed-upstream retitle 155134 [fixed in 3.0] errors in completion of executable's name forwarded 131101 ian@caliban.org tags 189006 + upstream tags 189006 + fixed-upstream retitle 189006 [fixed in 3.0] bash: tab completion on relative path directories thanks   Tags added: upstream Request was from Matthias Klose <doko@cs.tu-berlin.de> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 10 Oct 2003 22:59:13 +0000 From doko@cs.tu-berlin.de Fri Oct 10 17:59:12 2003 Return-path: Received: from mail.cs.tu-berlin.de [130.149.17.13] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1A86E3-0007CY-00; Fri, 10 Oct 2003 17:59:11 -0500 Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id AAA27014 for ; Sat, 11 Oct 2003 00:55:25 +0200 (MET DST) Received: (from doko@localhost) by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id h9AMtPj2000913; Sat, 11 Oct 2003 00:55:25 +0200 (MEST) From: Matthias Klose MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16263.14557.571565.287067@gargle.gargle.HOWL> Date: Sat, 11 Oct 2003 00:55:25 +0200 To: control@bugs.debian.org Subject: tagging readline and bash reports fixed upstream X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid Delivered-To: control@bugs.debian.org X-Spam-Status: No, hits=0.0 required=4.0 tests=none version=2.53-bugs.debian.org_2003_10_09 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_10_09 (1.174.2.15-2003-03-30-exp) retitle 179883 [fixed in 5.0] prompt overwriting with multibyte locale support tags 179883 + upstream tags 179883 + fixed-upstream retitle 172849 [fixed in 5.0] bug in the callback read-char interface tags 172849 + upstream tags 172849 + fixed-upstream tags 173659 + upstream tags 195678 + upstream tags 200871 + patch retitle 154063 [fixed in 5.0] readline redraws entire line for every key tags 154063 + fixed-upstream retitle 154884 [fixed in 5.0] input becomes extremely slow with long lines in MBCS tags 154884 + fixed-upstream tags 153974 + fixed-upstream tags 144585 + upstream tags 115500 + upstream retitle 65484 [fixed in 5.0] readline: namespace pollution tags 65484 + fixed-upstream tags 65484 + upstream tags 64203 + upstream tags 64203 + moreinfo tags 64203 + unreproducible tags 161057 + upstream tags 141292 + upstream tags 140914 + upstream tags 140914 + unreproducible tags 120910 + upstream tags 50853 + upstream tags 168331 + fixed-upstream retitle 168331 [fixed in 3.0] value of various assignments not documented tags 21645 + upstream tags 165533 + upstream tags 165533 + fixed-upstream retitle 165533 [fixed in 3.0] bash: PS4='``' bash -xc : segfaults tags 158035 + upstream tags 162952 + upstream tags 164134 + upstream tags 211426 + fixed-upstream retitle 211426 [fixed in 3.0] bash: stats maildir even though MAILCHECK=-1 tags 186218 + fixed-upstream tags 180290 + fixed-upstream tags 174744 + fixed-upstream tags 168321 + fixed-upstream tags 167003 + upstream tags 167003 + fixed-upstream retitle 167003 [fixed in 3.0] "read -a foo <<< $(echo)" segfaults tags 167002 + fixed-upstream retitle 167002 [fixed in 3.0] indirection not working with arrays tags 165212 + upstream tags 165212 + fixed-upstream retitle 165212 [fixed in 3.0] history substitution: !* can't handle <(foo) tags 164134 + upstream tags 164134 + fixed-upstream retitle 164134 [fixed in 3.0] bash: EINTR kills redirection tags 162952 + fixed-upstream retitle 162952 [fixed in 3.0] infinite loop with IFS="" and compgen -W tags 152847 + upstream tags 152847 + fixed-upstream retitle 152847 [fixed in 3.0] bash: auto-logout doesn't run .logout tags 120340 + upstream tags 7047 + upstream tags 7047 + wontfix tags 10494 + upstream tags 10494 + wontfix tags 61739 + upstream tags 62517 + upstream tags 72520 + upstream tags 86397 + upstream tags 90611 + upstream tags 110969 + upstream tags 159771 + upstream forwarded 159771 chet@po.cwru.edu merge 120340 159771 tags 186165 + upstream forwarded 186165 chet@po.cwru.edu forwarded 177517 chet@po.cwru.edu forwarded 175796 chet@po.cwru.edu forwarded 173982 chet@po.cwru.edu forwarded 173816 chet@po.cwru.edu forwarded 168701 chet@po.cwru.edu tags 168701 + upstream merge 116082 128997 tags 197965 + upstream tags 197965 + fixed-upstream retitle 193570 [fixed in 3.0] kill doesn't differenciate non-numbers tags 193570 + upstream tags 193570 + fixed-upstream forwarded 186994 chet@po.cwru.edu tags 186994 + upstream tags 186994 + fixed-upstream forwarded 176968 chet@po.cwru.edu tags 176968 + fixed-upstream retitle 176968 [fixed in 3.0] bash: printf abc output dissappears under bash prompt tags 174133 + fixed-upstream retitle 174133 [fixed in 3.0] bash: wait: not the child of this shell: not properly documented tags 168318 + upstream tags 168318 + fixed-upstream retitle 168318 [fixed in 3.0] bash: ${!PREFIX@} expansion not documented tags 168267 + upstream tags 168267 + fixed-upstream tags 155369 + upstream forwarded 111467 chet@po.cwru.edu severity 100743 minor forwarded 199042 chet@po.cwru.edu severity 199042 minor merge 100743 111467 merge 100743 199042 retitle 211693 [fixed in 3.0] bash -c 'segfaulting-command ; echo yes' doesn't report the segfault tags 211693 + upstream tags 211693 + fixed-upstream forwarded 204766 chet@po.cwru.edu tags 204766 + upstream forwarded 203767 chet@po.cwru.edu tags 203767 + upstream forwarded 199703 chet@po.cwru.edu tags 199703 + upstream tags 197440 + unreproducible retitle 195116 [fixed in 3.0] ferror called w/o always first calling clearerr results in spurious errors reported tags 195116 + upstream tags 195116 + fixed-upstream forwarded 192831 chet@po.cwru.edu tags 192831 + upstream merge 192831 203767 tags 187727 + upstream forwarded 187727 chet@po.cwru.edu tags 183352 + upstream tags 183352 + fixed-upstream retitle 183352 [fixed in 3.0] fix documentation about exit status of unset builtin forwarded 180075 chet@po.cwru.edu tags 180075 + upstream merge 190028 180075 tags 178828 + fixed-upstream retitle 178828 [fixed in 3.0] Missing trailing slash when completing directory names tags 173744 + f