Your message dated Mon, 12 May 2014 22:00:06 +0000 with message-id <e1wjygu-00013t...@franck.debian.org> and subject line Bug#747800: fixed in meep-mpich2 1.2.1-1 has caused the Debian Bug report #747800, regarding meep-mpich2: FTBFS: error: guile-config is broken 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.) -- 747800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: meep-mpich2 Version: 1.1.1-10 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140510 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh_testdir > mkdir -p debian/build-mpich2 > cat configure | \ > sed "s/PACKAGE_NAME='meep'/PACKAGE_NAME='meep-mpich2'/g" |\ > sed "s/PACKAGE='meep'/PACKAGE='meep-mpich2'/g" > configure-mpich2 > chmod 755 configure-mpich2 > cd debian/build-mpich2 && \ > F77=gfortran ../../configure-mpich2 --host=x86_64-linux-gnu > --build=x86_64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man > --infodir=\${prefix}/share/info --with-libctl=/usr/share/libctl3 > --enable-shared --with-pic --enable-cxx --with-mpi=yes > configure-mpich2: WARNING: unrecognized options: --enable-cxx > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking for x86_64-linux-gnu-g++... x86_64-linux-gnu-g++ > checking for C++ compiler default output file name... a.out > checking whether the C++ compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C++ compiler... yes > checking whether x86_64-linux-gnu-g++ accepts -g... yes > checking for style of include used by make... GNU > checking dependency style of x86_64-linux-gnu-g++... gcc3 > checking for mpic++... mpic++ > checking for MPI_Init... yes > checking for mpi.h... yes > checking for extra flag needed to combine stdio.h and mpi.h... none > checking build system type... x86_64-pc-linux-gnu > checking host system type... x86_64-pc-linux-gnu > checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc > checking whether we are using the GNU C compiler... yes > checking whether x86_64-linux-gnu-gcc accepts -g... yes > checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed > checking dependency style of x86_64-linux-gnu-gcc... gcc3 > checking for C++ compiler vendor... gnu > checking for a sed that does not truncate output... /bin/sed > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -E > checking for fgrep... /bin/grep -F > checking for ld used by x86_64-linux-gnu-gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1572864 > checking whether the shell understands some XSI constructs... yes > checking whether the shell understands "+="... yes > checking for /usr/bin/ld option to reload object files... -r > checking for x86_64-linux-gnu-objdump... x86_64-linux-gnu-objdump > checking how to recognize dependent libraries... pass_all > checking for x86_64-linux-gnu-ar... x86_64-linux-gnu-ar > checking for x86_64-linux-gnu-strip... x86_64-linux-gnu-strip > checking for x86_64-linux-gnu-ranlib... x86_64-linux-gnu-ranlib > checking command to parse /usr/bin/nm -B output from x86_64-linux-gnu-gcc > object... ok > checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking whether we are using the GNU C++ compiler... (cached) yes > checking whether mpic++ accepts -g... (cached) yes > checking dependency style of mpic++... (cached) gcc3 > checking how to run the C++ preprocessor... mpic++ -E > checking for objdir... .libs > checking if x86_64-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no > checking for x86_64-linux-gnu-gcc option to produce PIC... -fPIC -DPIC > checking if x86_64-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes > checking if x86_64-linux-gnu-gcc static flag -static works... yes > checking if x86_64-linux-gnu-gcc supports -c -o file.o... yes > checking if x86_64-linux-gnu-gcc supports -c -o file.o... (cached) yes > checking whether the x86_64-linux-gnu-gcc linker (/usr/bin/ld -m elf_x86_64) > supports shared libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for ld used by mpic++... /usr/bin/ld -m elf_x86_64 > checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes > checking whether the mpic++ linker (/usr/bin/ld -m elf_x86_64) supports > shared libraries... yes > checking for mpic++ option to produce PIC... -fPIC -DPIC > checking if mpic++ PIC flag -fPIC -DPIC works... yes > checking if mpic++ static flag -static works... no > checking if mpic++ supports -c -o file.o... yes > checking if mpic++ supports -c -o file.o... (cached) yes > checking whether the mpic++ linker (/usr/bin/ld -m elf_x86_64) supports > shared libraries... yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking for latex2html... no > configure-mpich2: WARNING: Cannot find latex2html in your path! > checking for sin in -lm... yes > checking for fftw_plan_dft_1d in -lfftw3... yes > checking for pkg-config... /usr/bin/pkg-config > checking for harminv >= 1.1... yes > checking HARMINV_CFLAGS... > checking HARMINV_LIBS... -lharminv > checking mpb.h usability... no > checking mpb.h presence... no > checking for mpb.h... no > checking for cblas_cgemm... no > checking for cblas_cgemm in -lgslcblas... yes > checking for gsl_sf_bessel_Jn in -lgsl... yes > checking for deflate in -lz... yes > checking for H5Pcreate in -lhdf5... yes > checking hdf5.h usability... yes > checking hdf5.h presence... yes > checking for hdf5.h... yes > checking for H5Pset_mpi... no > checking for H5Pset_fapl_mpio... yes > Looks like we have got 2 processors > checking for guile-config... guile-config > configure-mpich2: error: guile-config is broken > checking if linking to guile works... no > make: *** [configure-stamp-mpich2] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/05/10/meep-mpich2_1.1.1-10_unstable.log 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 EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---Source: meep-mpich2 Source-Version: 1.2.1-1 We believe that the bug you reported is fixed in the latest version of meep-mpich2, which is due to be installed in the Debian FTP archive. 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 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz <deb...@alteholz.de> (supplier of updated meep-mpich2 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...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sun, 11 May 2014 11:20:00 +0200 Source: meep-mpich2 Binary: meep-mpich2 libmeep-mpich2-7 libmeep-mpich2-dev Architecture: source amd64 Version: 1.2.1-1 Distribution: unstable Urgency: medium Maintainer: Thorsten Alteholz <deb...@alteholz.de> Changed-By: Thorsten Alteholz <deb...@alteholz.de> Description: libmeep-mpich2-7 - library for using parallel (OpenMPI) version of meep libmeep-mpich2-dev - development library for using parallel (OpenMPI) version of meep meep-mpich2 - software package for FDTD simulation, parallel (OpenMPI) version Closes: 744116 744463 747800 Changes: meep-mpich2 (1.2.1-1) unstable; urgency=medium . * new upstream version * soname changed to 7 * debian/rules: upstream ChangeLog is now called NEWS * debian/control: Standards Version to 3.9.5. (No changes needed). * debian/control: switch to dh 9 * debian/control: use guile 2.0 now (Closes: #747800) * debian/control: remove DM-Upload-Allowed: * debian/control: rebuild against new mpich (Closes: #744116) * debian/rules: use debhelper * debian/rules: use --with autoreconf (Closes: #744463) * debian/copyright: adapt years Checksums-Sha1: 7480f0a6f9244da11971a115fd4059307b49d11a 1475 meep-mpich2_1.2.1-1.dsc 1970c183aed60af4326bb51dea9c54e71e54b6d3 731272 meep-mpich2_1.2.1.orig.tar.gz 68f4e07c6d6c14ec4a16b9ad8107fce79f16294b 5344 meep-mpich2_1.2.1-1.debian.tar.xz 0583ec300c1edef02cffff89e7758218ff5cdc27 163962 meep-mpich2_1.2.1-1_amd64.deb a50c0f7a8ffb3ce6556cf3ef3851975d99dd903a 242282 libmeep-mpich2-7_1.2.1-1_amd64.deb d1fa033a117cefd39bba31fae4c5eb7ea984c98b 256782 libmeep-mpich2-dev_1.2.1-1_amd64.deb Checksums-Sha256: bd63ef2db7c1bb756c8dd84db34d2612766c534a61690296763cb05b7125edf3 1475 meep-mpich2_1.2.1-1.dsc f1f0683e5688d231f7dd1863939677148fc27a6744c03510e030c85d6c518ea5 731272 meep-mpich2_1.2.1.orig.tar.gz 073749546c7a194f2241a579ae9a5e2c6df81cb80cd728b87265c998a9ae8357 5344 meep-mpich2_1.2.1-1.debian.tar.xz 3997828e7247b2881bafb74cee212a0377c82f62232d186975b24afb3d2f5d74 163962 meep-mpich2_1.2.1-1_amd64.deb 72cfb2f4299fac21d36a1eb6fb5d177b00df3fe1930c8968772ffeea5695f82e 242282 libmeep-mpich2-7_1.2.1-1_amd64.deb 4e266d33108bd42d5e2c5e5f07f459c7f613c522980e94352b10d10f2162cbe9 256782 libmeep-mpich2-dev_1.2.1-1_amd64.deb Files: 6f21eca6421acf39975da2e335277def 163962 science optional meep-mpich2_1.2.1-1_amd64.deb e9787ea4bb0accae1f3aafd2ed060ca8 242282 libs optional libmeep-mpich2-7_1.2.1-1_amd64.deb 9ee82903063063dc6a7251b4f0ff83b2 256782 libdevel optional libmeep-mpich2-dev_1.2.1-1_amd64.deb 967bbb1e7a0b1aaf762e34e5ff1da290 1475 science optional meep-mpich2_1.2.1-1.dsc 9be2e743c3a832ae922de9d955d016c5 731272 science optional meep-mpich2_1.2.1.orig.tar.gz b027e3ee88354dd6262717b806202aa5 5344 science optional meep-mpich2_1.2.1-1.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlNw0oIACgkQ02K2KlS5mJAubQCgh6vQrBvVqRInv0kLK/I1Jwe2 T4oAnA8Wnq1csP5i4FEgxrQ5AS4y1W6z =g7P2 -----END PGP SIGNATURE-----
--- End Message ---
