Your message dated Mon, 17 Mar 2008 04:32:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#465575: fixed in bisonc++ 2.4.2-1
has caused the Debian Bug report #465575,
regarding bisonc++: FTBFS: FlexLexer.h:130: error: expected unqualified-id 
before numeric constant
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.)


-- 
465575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465575
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: bisonc++
Version: 2.4.1-1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080212 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

Relevant part:
> g++ -c -o scanner/o/11yylex.o -Wall -O3 scanner/yylex.cc
 > In file included from yylex.cc:394:
 > /usr/include/FlexLexer.h:130: error: expected unqualified-id before numeric 
 > constant
 > system - failure of system call (status 256)
 > system - failure of system call (status 256)
 > make: *** [build-stamp] Error 1

The full build log is available from:
        http://people.debian.org/~lucas/logs/2008/02/12

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 ---
Source: bisonc++
Source-Version: 2.4.2-1

We believe that the bug you reported is fixed in the latest version of
bisonc++, which is due to be installed in the Debian FTP archive:

bisonc++_2.4.2-1.diff.gz
  to pool/main/b/bisonc++/bisonc++_2.4.2-1.diff.gz
bisonc++_2.4.2-1.dsc
  to pool/main/b/bisonc++/bisonc++_2.4.2-1.dsc
bisonc++_2.4.2-1_i386.deb
  to pool/main/b/bisonc++/bisonc++_2.4.2-1_i386.deb
bisonc++_2.4.2.orig.tar.gz
  to pool/main/b/bisonc++/bisonc++_2.4.2.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Frank B. Brokken <[EMAIL PROTECTED]> (supplier of updated bisonc++ package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 16 Mar 2008 14:21:37 +0100
Source: bisonc++
Binary: bisonc++
Architecture: source i386
Version: 2.4.2-1
Distribution: unstable
Urgency: low
Maintainer: Frank B. Brokken <[EMAIL PROTECTED]>
Changed-By: Frank B. Brokken <[EMAIL PROTECTED]>
Description: 
 bisonc++   - Bison-style parser generator for C++
Closes: 465575 466637
Changes: 
 bisonc++ (2.4.2-1) unstable; urgency=low
 .
   * New upstream release. (Closes: #465575)
   * Modified package description. (Closes: #466637)
Files: 
 4ba93d458af6fb17c6a9abd2701f53cb 855 devel optional bisonc++_2.4.2-1.dsc
 25bdd10c02067bcfdaaddfe748055765 592677 devel optional 
bisonc++_2.4.2.orig.tar.gz
 e4c8d0bb434b39bc6b0f95a86a3560ec 9851 devel optional bisonc++_2.4.2-1.diff.gz
 023e236465f88d424f18e97fa92fa14a 330474 devel optional 
bisonc++_2.4.2-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH3fLWpdwBkPlyvgMRAnsoAJ4kVov5GUS7f9lIgWg2NMvSI9KC2QCcDsOi
DDOGgUTFUtUD9QxGCj3ylnU=
=szKC
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to