Your message dated Sun, 23 Aug 2009 04:03:22 +0000
with message-id <e1mf4ic-0000ch...@ries.debian.org>
and subject line Bug#542970: fixed in libsemanage 2.0.33-2
has caused the Debian Bug report #542970,
regarding libsemanage: FTBFS: <stdout>:496: error: expected expression at end
of input
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 ow...@bugs.debian.org
immediately.)
--
542970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsemanage
Version: 2.0.33-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090822 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> cc -Wall -g -O2 -I../include -I/usr/include -D_GNU_SOURCE -fPIC -DSHARED -c
> -o conf-scan.lo conf-scan.c
> <stdout>:496: error: expected expression at end of input
> make[3]: *** [conf-scan.lo] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2009/08/22/libsemanage_2.0.33-1_lsid64.buildlog
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. Internet was not
accessible from the build systems.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
Source: libsemanage
Source-Version: 2.0.33-2
We believe that the bug you reported is fixed in the latest version of
libsemanage, which is due to be installed in the Debian FTP archive:
libsemanage-ruby1.8_2.0.33-2_amd64.deb
to pool/main/libs/libsemanage/libsemanage-ruby1.8_2.0.33-2_amd64.deb
libsemanage1-dev_2.0.33-2_amd64.deb
to pool/main/libs/libsemanage/libsemanage1-dev_2.0.33-2_amd64.deb
libsemanage1_2.0.33-2_amd64.deb
to pool/main/libs/libsemanage/libsemanage1_2.0.33-2_amd64.deb
libsemanage_2.0.33-2.diff.gz
to pool/main/libs/libsemanage/libsemanage_2.0.33-2.diff.gz
libsemanage_2.0.33-2.dsc
to pool/main/libs/libsemanage/libsemanage_2.0.33-2.dsc
python-semanage_2.0.33-2_amd64.deb
to pool/main/libs/libsemanage/python-semanage_2.0.33-2_amd64.deb
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 542...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Manoj Srivastava <sriva...@debian.org> (supplier of updated libsemanage 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 ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Format: 1.8
Date: Sat, 22 Aug 2009 17:19:53 -0500
Source: libsemanage
Binary: libsemanage1 libsemanage1-dev libsemanage-ruby1.8 python-semanage
Architecture: source amd64
Version: 2.0.33-2
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava <sriva...@debian.org>
Changed-By: Manoj Srivastava <sriva...@debian.org>
Description:
libsemanage-ruby1.8 - Ruby bindings to for SELinux policy manipulation tools
libsemanage1 - shared libraries used by SELinux policy manipulation tools
libsemanage1-dev - Header files and libraries for SELinux policy manipulation
tools
python-semanage - Python bindings for SELinux policy manipulation tools
Closes: 542970
Changes:
libsemanage (2.0.33-2) unstable; urgency=low
.
* Hmm. More timing issues with building in parallel. With the new
changes, the jobserver no longer seems disabled, which should take
care of this. In any case, I can't reproduce it even when building in
parallel now.
Bug fix: "FTBFS: <stdout>:496: error: expected expression at end
of input", thanks to Lucas Nussbaum (Closes: #542970).
Checksums-Sha1:
712c139ac11be7c6e6b101ddf8ff4c52778c20c5 1361 libsemanage_2.0.33-2.dsc
0150cdd3c7051ba92e86f8db1cd911e2152abe31 68610 libsemanage_2.0.33-2.diff.gz
a377910ea1e75ddbcba13fdceaa60202992a2d16 97926 libsemanage1_2.0.33-2_amd64.deb
a9cb13970aa698fca9ae0de1b62404578f7d5f25 451924
libsemanage1-dev_2.0.33-2_amd64.deb
ccdf99919899b2629ecbd70016d05469ab89567f 62648
libsemanage-ruby1.8_2.0.33-2_amd64.deb
45ad7ccedf744833eacf4bcfdf59c024880c029a 75662
python-semanage_2.0.33-2_amd64.deb
Checksums-Sha256:
c18c81611d19d029021c813133e1c5eabc67895b13987de46e6352edb5be8939 1361
libsemanage_2.0.33-2.dsc
26cd92bf4931ebe26eddc3696e28c490973a6ec62f9ac62f29b4091544bef393 68610
libsemanage_2.0.33-2.diff.gz
ab97a6f5bfb0746cf84d13efea4d23e2a6c7f45c30fa8ea7568574317e338300 97926
libsemanage1_2.0.33-2_amd64.deb
28029757152a7b2273fe118fcfcc955a88c32ec4167a45f3e24b22c314f7166a 451924
libsemanage1-dev_2.0.33-2_amd64.deb
76fb2ee0088c6f8e88f204d439393b3142b8ddb11362660328df8983450a2740 62648
libsemanage-ruby1.8_2.0.33-2_amd64.deb
232e0a6100c10c3127eb196f303db91c72f9a826305f14d368e05241b45c8674 75662
python-semanage_2.0.33-2_amd64.deb
Files:
fbf1011e9e8d5e71785e921201274795 1361 libdevel optional
libsemanage_2.0.33-2.dsc
6d23952595acd78599087406d0762bc1 68610 libdevel optional
libsemanage_2.0.33-2.diff.gz
f62459b34ae0400d1c8636a28398c71c 97926 libs optional
libsemanage1_2.0.33-2_amd64.deb
6b95a622de4c15715ea089595bc74c67 451924 libdevel optional
libsemanage1-dev_2.0.33-2_amd64.deb
2cabc90a384f4c51300d31fbeddf4d44 62648 ruby optional
libsemanage-ruby1.8_2.0.33-2_amd64.deb
4a9499ca6fe680d904349a2ecc6eb494 75662 python optional
python-semanage_2.0.33-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13-svn0 (GNU/Linux)
iEYEAREDAAYFAkqQj6YACgkQIbrau78kQkyOPgCgh1QLOWXtllDv+ep+ATzKdVoo
pKEAnR7MbjsdbRdks8cwpR/OWiGT9c2Y
=kV/D
-----END PGP SIGNATURE-----
--- End Message ---
