Your message dated Wed, 7 May 2008 11:39:52 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: bash: echo -e no longer interprets \nnn
has caused the Debian Bug report #478234,
regarding bash: echo -e no longer interprets \nnn
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
478234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478234
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libmcal
Version: 0.6-16
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080425 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now
the default on most architectures (even if it's not the case on i386 yet).
Feel free to downgrade this bug to 'important' if your package is only built
on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with
gcc 4.2).
Relevant part:
> gcc -c -fPIC -O2 -D_REENTRANT -Wall -Imstore -Iicap -I. -o mcal.lo mcal.c
> In file included from mcal.c:37:
> drivers.c:1: error: stray '\' in program
> drivers.c:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before
> numeric constant
> drivers.c:1: error: stray '\' in program
> mcal.c: In function 'cal_getdriver':
> mcal.c:68: error: 'driver_registry' undeclared (first use in this function)
> mcal.c:68: error: (Each undeclared identifier is reported only once
> mcal.c:68: error: for each function it appears in.)
> make[1]: *** [mcal.lo] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2008/04/25
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment. Internet was not accessible from the build systems.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
tag 478234 + wontfix
thanks
Yes, this change was intended, upstream writes:
"changed from 3.1 to 3.2, for Posix conformance. `echo -e' (and the
corresponding xpg_echo shell option) now conform to the POSIX standard
and accept 0-3 octal digits after a (required) leading `\0'.
The xpg_echo and `echo -e' code should be identical. There are lots
of ways to indicate that backslash escapes should be interpreted --
maybe too many -- but when they are, they should behave consistently.
This is why portable applications should use printf."
--- End Message ---
