Bug#375349: autoconf: puts |#_!!_#| in output files

2006-06-25 Thread Steinar H. Gunderson
Package: autoconf
Version: 2.59.cvs.2006.05.13-1
Severity: important

Newer autoconf versions seem to use |#_!!_#| as an internal separator
during the AC_OUTPUT phase; this is supposed to be sedded away again at
the very end, but for some reason it doesn't; see for instance #373953,
where it's creeping into PREFIX and whatnot.

I've verified that this doesn't happen in 2.59a-9; it surfaced in the
first CVS version in the archive (2.59.cvs.2006.05.13-1).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16trofastxen
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)

Versions of packages autoconf depends on:
ii  debianutils   2.16.1 Miscellaneous utilities specific t
ii  m41.4.4-1a macro processing language
ii  perl  5.8.8-6Larry Wall's Practical Extraction 

Versions of packages autoconf recommends:
ii  automake1.4 [automaken]  1:1.4-p6-10 A tool for generating GNU Standard
ii  automake1.7 [automaken]  1.7.9-8 A tool for generating GNU Standard
ii  automake1.8 [automaken]  1.8.5-4 A tool for generating GNU Standard
ii  automake1.9 [automaken]  1.9.6-4 A tool for generating GNU Standard

-- debconf-show failed


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#375349: autoconf: puts |#_!!_#| in output files

2006-06-25 Thread Ralf Wildenhues
[ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375349 ]

Hi Steinar,

Thanks much for reporting this.

* Steinar H. Gunderson wrote on Sun, Jun 25, 2006 at 02:31:21PM CEST:
> Package: autoconf
> Version: 2.59.cvs.2006.05.13-1
> Severity: important
> 
> Newer autoconf versions seem to use |#_!!_#| as an internal separator
> during the AC_OUTPUT phase; this is supposed to be sedded away again at
> the very end, but for some reason it doesn't; see for instance #373953,
> where it's creeping into PREFIX and whatnot.
> 
> I've verified that this doesn't happen in 2.59a-9; it surfaced in the
> first CVS version in the archive (2.59.cvs.2006.05.13-1).

Confirmed with 2.59.cvs.2006.05.13-1.  I'll follow up on #373953.
Have you seen this or a similar issue with any other packages?

Cheers,
Ralf


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#375349: autoconf: puts |#_!!_#| in output files

2006-06-25 Thread Steinar H. Gunderson
On Sun, Jun 25, 2006 at 04:17:29PM +0200, Ralf Wildenhues wrote:
> Confirmed with 2.59.cvs.2006.05.13-1.  I'll follow up on #373953.
> Have you seen this or a similar issue with any other packages?

I checked this, and it's not a bug in autoconf, IMO.

mkconfig.rb parses config.status for s,,, lines, duplicating them to create
another configuration file, but it doesn't understand the |#_!!_#| trick.
I simply made it sed it away itself, and the package was fixed.

Decide for yourself if you want to close this as "not a bug", or if you
actually think it should be changed back in autoconf.

/* Steinar */
-- 
Homepage: http://www.sesse.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]