GNU logs - #9916, boring messages

Message sent to bug-libtool@HIDDEN:

Subject: bug#9916: [PATCH] echo: fix octal escaping with \1...\7
Resent-From: Eric Blake <eblake@HIDDEN>
Original-Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Resent-CC: bug-libtool@HIDDEN
Resent-Date: Mon, 31 Oct 2011 13:16:01 +0000
Resent-Message-ID: <handler.9916.B.132006691014311 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Mike Frysinger <vapier@HIDDEN>
Cc: herbert@HIDDEN, dash@HIDDEN, 9916 <at> debbugs.gnu.org
Message-ID: <4EAE9ECB.4040607@HIDDEN>
Date: Mon, 31 Oct 2011 07:12:43 -0600
From: Eric Blake <eblake@HIDDEN>
Organization: Red Hat
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.23) Gecko/20110928 Fedora/3.1.15-1.fc14
	Lightning/1.0b3pre Mnenhy/0.8.4 Thunderbird/3.1.15
MIME-Version: 1.0
References: <20111031034146.GA19477@HIDDEN>
	<201110310023.45138.vapier@HIDDEN>
In-Reply-To: <201110310023.45138.vapier@HIDDEN>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: list
Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org

[adding bug-libtool]

On 10/30/2011 10:23 PM, Mike Frysinger wrote:
> On Sunday 30 October 2011 23:41:58 Herbert Xu wrote:
>> Mike Frysinger wrote:
>>> POSIX states that octal escape sequences should take the form \0num
>>> when using echo.  dash however additionally treats \num as an octal
>>> sequence.  This breaks some packages (like libtool) who attempt to
>>> use strings with these escape sequences via variables to execute sed
>>> (since sed ends up getting passed a byte instead of a literal \1).

That's a bug in libtool for using "echo '\1'" and expecting sane 
behavior.  Can you provide more details on this libtool bug, so we can 
get it fixed in libtool?  Or perhaps it has already been fixed in modern 
libtool, and you are just encountering it in an older version?

>>
>> OK this is a bit of problem.  From our conversation I had the
>> impression that you were referring to the lack of support of
>> escape codes, rather than unwanted support.
>>
>> If it was the former I could easily add it if POSIX said so,
>> however, as this is an existing feature there may well be scripts
>> out there that depend on it.  So removing it is not an option
>> unless it is explicitly forbidden by POSIX.
>
> i'm not seeing how this jives with dash's goal.  if it intends to be a
> fast/small POSIX compliant shell while punting (almost) all the rest, then why
> carry additional functionality that POSIX doesn't even mention in passing ?
> this isn't "documented but optional extended functionality", but rather the
> realm of "anything goes".  otherwise we approach the same realm that dash was
> created to avoid -- carrying lots of cruft that slow things down because
> scripts use it rather than POSIX mandating it.
>
> as a comparison, bash/ksh/tcsh/zsh/busybox[ash] all behave the way my patch
> updates dash to operate ... i would test more shells, but these tend to be the
> standards that everyone compares against.  i can't see people writing scripts
> that only work under dash either.
>
>> In any case, scripts that rely on escape codes like this are
>> simply broken and should either be fixed to use printf or just
>> run with #!/bin/bash.
>
> they're relying on these escape codes not being interpreted as escape codes
> (which every other shell appears to do), not the other way around

Scripts that rely on a certain interpretation of "echo '\1'" are broken 
regardless of how dash behaves; but that said, since POSIX doesn't 
require dash's current behavior, and since the proposed patch makes dash 
both smaller and more like other shells in treating it as an extension 
that means a literal 1 rather than an octal escape, I would be in favor 
of making the change in dash.

-- 
Eric Blake   eblake@HIDDEN    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Eric Blake <eblake@HIDDEN>
Subject: bug#9916: Acknowledgement ([PATCH] echo: fix octal escaping with
 \1...\7)
Message-ID: <handler.9916.B.132006691014311.ack <at> debbugs.gnu.org>
References: <4EAE9ECB.4040607@HIDDEN>
X-Gnu-PR-Message: ack 9916
X-Gnu-PR-Package: libtool
X-Gnu-PR-Keywords: patch
Reply-To: 9916 <at> debbugs.gnu.org
Date: Mon, 31 Oct 2011 13:16:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-libtool@HIDDEN

If you wish to submit further information on this problem, please
send it to 9916 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
9916: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D9916
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-libtool@HIDDEN:

Subject: bug#9916: [PATCH] echo: fix octal escaping with \1...\7
Resent-From: Mike Frysinger <vapier@HIDDEN>
Original-Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Resent-CC: bug-libtool@HIDDEN
Resent-Date: Mon, 31 Oct 2011 18:43:01 +0000
Resent-Message-ID: <handler.9916.B.132008652319208 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Eric Blake <eblake@HIDDEN>
Cc: herbert@HIDDEN, dash@HIDDEN, 9916 <at> debbugs.gnu.org
From: Mike Frysinger <vapier@HIDDEN>
Organization: wh0rd.org
Date: Mon, 31 Oct 2011 14:39:37 -0400
User-Agent: KMail/1.13.7 (Linux/3.1.0-rc4; KDE/4.6.5; x86_64; ; )
References: <20111031034146.GA19477@HIDDEN>
	<201110310023.45138.vapier@HIDDEN>
	<4EAE9ECB.4040607@HIDDEN>
In-Reply-To: <4EAE9ECB.4040607@HIDDEN>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart12134331.pGt6qVsan4";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201110311439.38413.vapier@HIDDEN>
Precedence: list
Sender: debbugs-submit-bounces <at> debbugs.gnu.org
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org

--nextPart12134331.pGt6qVsan4
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Monday 31 October 2011 09:12:43 Eric Blake wrote:
> On 10/30/2011 10:23 PM, Mike Frysinger wrote:
> > On Sunday 30 October 2011 23:41:58 Herbert Xu wrote:
> >> Mike Frysinger wrote:
> >>> POSIX states that octal escape sequences should take the form \0num
> >>> when using echo.  dash however additionally treats \num as an octal
> >>> sequence.  This breaks some packages (like libtool) who attempt to
> >>> use strings with these escape sequences via variables to execute sed
> >>> (since sed ends up getting passed a byte instead of a literal \1).
>=20
> That's a bug in libtool for using "echo '\1'" and expecting sane
> behavior.  Can you provide more details on this libtool bug, so we can
> get it fixed in libtool?  Or perhaps it has already been fixed in modern
> libtool, and you are just encountering it in an older version?

i plan on digging through the relevant packages and posting patches where=20
applicable.  i might be wrong about the libtool side, but do know of at lea=
st=20
one ax m4 file using it (which is what started this rat hole in the first=20
place).  but i consider that a parallel issue :).

> >> OK this is a bit of problem.  From our conversation I had the
> >> impression that you were referring to the lack of support of
> >> escape codes, rather than unwanted support.
> >>=20
> >> If it was the former I could easily add it if POSIX said so,
> >> however, as this is an existing feature there may well be scripts
> >> out there that depend on it.  So removing it is not an option
> >> unless it is explicitly forbidden by POSIX.
> >=20
> > i'm not seeing how this jives with dash's goal.  if it intends to be a
> > fast/small POSIX compliant shell while punting (almost) all the rest,
> > then why carry additional functionality that POSIX doesn't even mention
> > in passing ? this isn't "documented but optional extended
> > functionality", but rather the realm of "anything goes".  otherwise we
> > approach the same realm that dash was created to avoid -- carrying lots
> > of cruft that slow things down because scripts use it rather than POSIX
> > mandating it.
> >=20
> > as a comparison, bash/ksh/tcsh/zsh/busybox[ash] all behave the way my
> > patch updates dash to operate ... i would test more shells, but these
> > tend to be the standards that everyone compares against.  i can't see
> > people writing scripts that only work under dash either.
> >=20
> >> In any case, scripts that rely on escape codes like this are
> >> simply broken and should either be fixed to use printf or just
> >> run with #!/bin/bash.
> >=20
> > they're relying on these escape codes not being interpreted as escape
> > codes (which every other shell appears to do), not the other way around
>=20
> Scripts that rely on a certain interpretation of "echo '\1'" are broken
> regardless of how dash behaves;

sure, i'm not arguing that logic

> but that said, since POSIX doesn't
> require dash's current behavior, and since the proposed patch makes dash
> both smaller and more like other shells in treating it as an extension
> that means a literal 1 rather than an octal escape, I would be in favor
> of making the change in dash.

right, that's what i'm going for
=2Dmike

--nextPart12134331.pGt6qVsan4
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQIcBAABAgAGBQJOrutqAAoJEEFjO5/oN/WBx1oP/0skpIcRcE2b1vUGPUVKwOWk
2Vqa6q7ALDEQRaqKW30cLpPk21y8/kNY4VAi9vLHT8aUbKHNdwTiS2BWZS0Vqp5i
8sIwrLkPIyVx91dZPzCSAstK99e5QjUBbJt2rqtepfYfFyY7KRASa0DyDG3WBofO
hFR4hBC9EBPLwYCjzyUvjmKihLlQSGmFjDIZ4HmLHeeXLRUm05nNcXPPuaxUMgBV
nA8YFMgNLydrt6wso/UE7M6ksQLzwGirS2PE4BB9c7ekd9WAEO8G88xUkWTidGe7
K++vqrlobiJPY6ROmFvxV740AS1FKz0MTm5TwzyrWbQ4vN5cXwpdj7vMrY4ee+B+
5bTH+WeelqJIqpKxNsIuEQHelpKU5BFySfBEkUTIvs0GCQyTnjmHVosLCXDF5rK1
MKoOb56aLqK0zJC2tFtD7Dmrv31hTkUNYGAYSZtYUcetxbSGDdfYCClVZjy3h3jQ
cuIZxRo863ROCYvo5QLgzwaOAuaWChgg/KJ0BQkxzIW13aiNN38CPbHVjBRKFsfa
r7C6EnHWHXdIcmMzyClGS0wqjEnnVxM6HZQojZMnR5gLfrglx3NVIslHOJAcus0Z
u7Aa4vIOoGG50nEvU/7FXboc3j2G9R9BzBJo9w3WEBNP755LzjBAlcOlac2UUs4A
DAcAC77KKAbchnu8esGX
=SuOL
-----END PGP SIGNATURE-----

--nextPart12134331.pGt6qVsan4--

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.