Bug#642922: regression: "sh -c" change causes FTBFS
Package: dash
Version: 0.5.7-1
Severity: important
Tags: patch
Hello,
Bugs #642706 (bin-prot FTBFS) and #642835 (sexplib310 FTBFS) can be
fixed by reverting the patch submitted at [1]. I don't understand why.
[1] http://thread.gmane.org/gmane.comp.shells.dash/556
While investigating #642706, in the failing case, I observed that a
cpp process called with "sh -c" gets SIGPIPE while writing to
stderr. In the succeeding case, the write is successful, and is read
by the ocamlbuild process that started "sh -c cpp ...".
Cheers,
--
Stéphane
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dash depends on:
ii debianutils 4.0.2
ii dpkg 1.16.0.3
ii libc6 2.13-21
dash recommends no packages.
dash suggests no packages.
-- debconf information:
* dash/sh: true
diff -u dash-0.5.7/debian/changelog dash-0.5.7/debian/changelog
--- dash-0.5.7/debian/changelog
+++ dash-0.5.7/debian/changelog
@@ -1,3 +1,10 @@
+dash (0.5.7-1.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Revert http://thread.gmane.org/gmane.comp.shells.dash/556
+
+ -- Stéphane Glondu <glondu@debian.org> Sun, 25 Sep 2011 19:05:10 +0200
+
dash (0.5.7-1) unstable; urgency=low
* new upstream release.
only in patch2:
unchanged:
--- dash-0.5.7.orig/src/main.c
+++ dash-0.5.7/src/main.c
@@ -171,7 +171,7 @@
state3:
state = 4;
if (minusc)
- evalstring(minusc, sflag ? 0 : EV_EXIT);
+ evalstring(minusc, 0);
if (sflag || minusc == NULL) {
state4: /* XXX ??? - why isn't this before the "if" statement */
Reply to: