Your message dated Tue, 29 May 2012 07:56:23 +0000
with message-id <e1szhhz-0000q0...@franck.debian.org>
and subject line Bug#667353: fixed in recoverjpeg 2.0-3.1
has caused the Debian Bug report #667353,
regarding recoverjpeg: ftbfs with GCC-4.7
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.)
--
667353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: recoverjpeg
Version: 2.0-3
Severity: important
Tags: sid wheezy
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.7
The package fails to build in a test rebuild on at least amd64 with
gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The
severity of this report may be raised before the wheezy release.
recovermov.cpp:98:50: error: 'getopt' was not declared in this scope
The full build log can be found at:
http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/recoverjpeg_2.0-3_unstable-gcc47.log
The last lines of the build log are at the end of this report.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
[...]
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
dh_auto_build -a
make[1]: Entering directory `/«PKGBUILDDIR»'
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\"
-DPACKAGE=\"recoverjpeg\" -DVERSION=\"2.0\" -I. -g -O2 -c recoverjpeg.c
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\"
-DPACKAGE=\"recoverjpeg\" -DVERSION=\"2.0\" -I. -g -O2 -c utils.c
gcc -g -O2 -o recoverjpeg recoverjpeg.o utils.o
g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\"
-DPACKAGE=\"recoverjpeg\" -DVERSION=\"2.0\" -I. -g -O2 -c -o recovermov.o
recovermov.cpp
recovermov.cpp: In function 'int main(int, char**)':
recovermov.cpp:98:50: error: 'getopt' was not declared in this scope
recovermov.cpp:101:31: error: 'optarg' was not declared in this scope
recovermov.cpp:114:11: error: 'optind' was not declared in this scope
make[1]: *** [recovermov.o] Error 1
make[1]: Leaving directory `/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: recoverjpeg
Source-Version: 2.0-3.1
We believe that the bug you reported is fixed in the latest version of
recoverjpeg, which is due to be installed in the Debian FTP archive:
recoverjpeg_2.0-3.1.debian.tar.gz
to main/r/recoverjpeg/recoverjpeg_2.0-3.1.debian.tar.gz
recoverjpeg_2.0-3.1.dsc
to main/r/recoverjpeg/recoverjpeg_2.0-3.1.dsc
recoverjpeg_2.0-3.1_amd64.deb
to main/r/recoverjpeg/recoverjpeg_2.0-3.1_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 667...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose <d...@debian.org> (supplier of updated recoverjpeg 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: SHA1
Format: 1.8
Date: Thu, 05 Apr 2012 09:19:41 +0000
Source: recoverjpeg
Binary: recoverjpeg
Architecture: source amd64
Version: 2.0-3.1
Distribution: unstable
Urgency: low
Maintainer: William Vera <bi...@billy.com.mx>
Changed-By: Matthias Klose <d...@debian.org>
Description:
recoverjpeg - tool to recover JPEG images from a filesystem image
Closes: 667353
Changes:
recoverjpeg (2.0-3.1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix FTBFS with gcc 4.7 by fixing missing <unistd.h> include (Cyril
Brulebois). Closes: #667353.
Checksums-Sha1:
62f6c488f5bca7db6257eb5c687adc1b760fb33b 1120 recoverjpeg_2.0-3.1.dsc
fb6d6dacff5c3c69c0f36414b3d151d71712db93 4672 recoverjpeg_2.0-3.1.debian.tar.gz
b171e802b9282cee3aa317b9ec22d21595af0af6 21066 recoverjpeg_2.0-3.1_amd64.deb
Checksums-Sha256:
25f8c0d25bff7c284379733c6cae793811e0f389d431e82c5789db288095db69 1120
recoverjpeg_2.0-3.1.dsc
2737b85f60029e8bb4bb6f53370e76c77f91c6e4f2d1dc7d377df84b6921210c 4672
recoverjpeg_2.0-3.1.debian.tar.gz
fa79ccea1c070596ffcca16b1345fb7b95226e0bc3b921fa53326ea7fe661b1a 21066
recoverjpeg_2.0-3.1_amd64.deb
Files:
6744fbef8c93192f4ab9c0ddb4b614aa 1120 graphics optional recoverjpeg_2.0-3.1.dsc
8ec02667b0e1a7fee8a0ed13740233dc 4672 graphics optional
recoverjpeg_2.0-3.1.debian.tar.gz
b6dfbd05891c654df1efebdd34b94de6 21066 graphics optional
recoverjpeg_2.0-3.1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk/EfSMACgkQStlRaw+TLJyHWACcDpiiiu+NSJnYcJsjLKZpJbjZ
uU4An25ay23M3TIN9Q5zUYjL7DFEo+rS
=YWQL
-----END PGP SIGNATURE-----
--- End Message ---
