Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
On 24/12/09 at 19:56 -0500, Jeremy T. Bouse wrote: Lucas Nussbaum wrote: On 24/12/09 at 13:02 -0500, Jeremy T. Bouse wrote: Lucas Nussbaum wrote: On 24/12/09 at 12:04 -0500, Jeremy T. Bouse wrote: I suggest there might be something wrong with the amd64 build box you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version from the mirrors and rebuilt under a pbuilder chroot and it built successfully as well. The -4 version of the package had a problem in the debian/rules that caused this behavior but it was fixed in the -5 release. Could you please diff your log with mine, to see if the problem was possibly caused by different build-dep versions ? I'm building on i386 as my amd64 boxes are currently still offline along with my hppa and alpha machines. The official amd64 buildd I sent the URL that was available for the log. When looking through it I didn't see any failures. However that log format and your log format are completely different and do not lend themselves to diff comparison. I'm talking about a build in an up-to-date sid chroot, not something that happened 10 days ago. Here's the build for me... The source is from the mirror using dget and not from the git repo [1] that it was originally built and submitted to the mirror from. Prior to the build I did a 'pbuilder update' for DIST=sid to ensure it was current. It seems that under some conditions, running make will determine that automake need to be re-run. But you don't build-depend on automake, causing the build failure. So the fix is to add automake to your build-depends. It might be caused by the lack of precision of ext3 vs tmpfs: I'm building on tmpfs, which has sub-second precision. (ext4 has that too). Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
Source: libgcgi Version: 0.9.5.dfsg-5 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /usr/bin/fakeroot debian/rules clean dh_testdir dh_testroot dh_auto_clean dh_clean find . \( -type d -a -name .deps -prune -exec rm -rf {} \; \) dpatch deapply-all 01_update_libtool not applied to ./ . rm -rf patch-stamp patch-stampT debian/patched dpkg-source -b libgcgi-0.9.5.dfsg dpkg-source: info: using source format `1.0' dpkg-source: info: building libgcgi using existing libgcgi_0.9.5.dfsg.orig.tar.gz dpkg-source: info: building libgcgi in libgcgi_0.9.5.dfsg-5.diff.gz dpkg-source: warning: executable mode 0755 of 'debian/patches/01_update_libtool.dpatch' will not be represented in diff dpkg-source: info: building libgcgi in libgcgi_0.9.5.dfsg-5.dsc debian/rules build test -d debian/patched || install -d debian/patched dpatch apply-all applying patch 01_update_libtool to ./ ... ok. dpatch cat-all patch-stampT mv -f patch-stampT patch-stamp dh_testdir find . \( -type f -a -name Makefile.* -prune -exec touch {} \; \) # Add here commands to configure the package. CFLAGS=-Wall -g -O2 ./configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --with-openssl checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes /build/user-libgcgi_0.9.5.dfsg-5-amd64-eqxp1F/libgcgi-0.9.5.dfsg/config/missing: Unknown `--run' option Try `/build/user-libgcgi_0.9.5.dfsg-5-amd64-eqxp1F/libgcgi-0.9.5.dfsg/config/missing --help' for more information configure: WARNING: `missing' script is too old or missing 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 for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... 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 x86_64-linux-gnu-gcc accepts -g... yes checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of x86_64-linux-gnu-gcc... gcc3 checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking whether make sets $(MAKE)... (cached) yes checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for a sed that does not truncate output... /bin/sed 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... 3458764513820540925 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... no checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for x86_64-linux-gnu-ar... no checking for ar... ar checking for x86_64-linux-gnu-strip... no checking for strip... strip checking for x86_64-linux-gnu-ranlib... no checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from x86_64-linux-gnu-gcc object... ok 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 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
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
I suggest there might be something wrong with the amd64 build box you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version from the mirrors and rebuilt under a pbuilder chroot and it built successfully as well. The -4 version of the package had a problem in the debian/rules that caused this behavior but it was fixed in the -5 release. Jeremy [1]https://buildd.debian.org/fetch.cgi?pkg=libgcgi;ver=0.9.5.dfsg-5;arch=amd64;stamp=1260598069 Lucas Nussbaum wrote: Source: libgcgi Version: 0.9.5.dfsg-5 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /usr/bin/fakeroot debian/rules clean dh_testdir dh_testroot dh_auto_clean dh_clean find . \( -type d -a -name .deps -prune -exec rm -rf {} \; \) dpatch deapply-all 01_update_libtool not applied to ./ . rm -rf patch-stamp patch-stampT debian/patched dpkg-source -b libgcgi-0.9.5.dfsg dpkg-source: info: using source format `1.0' dpkg-source: info: building libgcgi using existing libgcgi_0.9.5.dfsg.orig.tar.gz dpkg-source: info: building libgcgi in libgcgi_0.9.5.dfsg-5.diff.gz dpkg-source: warning: executable mode 0755 of 'debian/patches/01_update_libtool.dpatch' will not be represented in diff dpkg-source: info: building libgcgi in libgcgi_0.9.5.dfsg-5.dsc debian/rules build test -d debian/patched || install -d debian/patched dpatch apply-all applying patch 01_update_libtool to ./ ... ok. dpatch cat-all patch-stampT mv -f patch-stampT patch-stamp dh_testdir find . \( -type f -a -name Makefile.* -prune -exec touch {} \; \) # Add here commands to configure the package. CFLAGS=-Wall -g -O2 ./configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --with-openssl checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes /build/user-libgcgi_0.9.5.dfsg-5-amd64-eqxp1F/libgcgi-0.9.5.dfsg/config/missing: Unknown `--run' option Try `/build/user-libgcgi_0.9.5.dfsg-5-amd64-eqxp1F/libgcgi-0.9.5.dfsg/config/missing --help' for more information configure: WARNING: `missing' script is too old or missing 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 for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... 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 x86_64-linux-gnu-gcc accepts -g... yes checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of x86_64-linux-gnu-gcc... gcc3 checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking whether make sets $(MAKE)... (cached) yes checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for a sed that does not truncate output... /bin/sed 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... 3458764513820540925 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... no checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for x86_64-linux-gnu-ar... no checking for ar... ar checking for x86_64-linux-gnu-strip... no checking for strip... strip checking for x86_64-linux-gnu-ranlib... no checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from x86_64-linux-gnu-gcc object... ok 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 for objdir... .libs checking if x86_64-linux-gnu-gcc supports
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
On 24/12/09 at 12:04 -0500, Jeremy T. Bouse wrote: I suggest there might be something wrong with the amd64 build box you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version from the mirrors and rebuilt under a pbuilder chroot and it built successfully as well. The -4 version of the package had a problem in the debian/rules that caused this behavior but it was fixed in the -5 release. Could you please diff your log with mine, to see if the problem was possibly caused by different build-dep versions ? Thanks Lucas signature.asc Description: Digital signature
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
Lucas Nussbaum wrote: On 24/12/09 at 12:04 -0500, Jeremy T. Bouse wrote: I suggest there might be something wrong with the amd64 build box you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version from the mirrors and rebuilt under a pbuilder chroot and it built successfully as well. The -4 version of the package had a problem in the debian/rules that caused this behavior but it was fixed in the -5 release. Could you please diff your log with mine, to see if the problem was possibly caused by different build-dep versions ? I'm building on i386 as my amd64 boxes are currently still offline along with my hppa and alpha machines. The official amd64 buildd I sent the URL that was available for the log. When looking through it I didn't see any failures. However that log format and your log format are completely different and do not lend themselves to diff comparison. Jeremy signature.asc Description: OpenPGP digital signature
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
On 24/12/09 at 13:02 -0500, Jeremy T. Bouse wrote: Lucas Nussbaum wrote: On 24/12/09 at 12:04 -0500, Jeremy T. Bouse wrote: I suggest there might be something wrong with the amd64 build box you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version from the mirrors and rebuilt under a pbuilder chroot and it built successfully as well. The -4 version of the package had a problem in the debian/rules that caused this behavior but it was fixed in the -5 release. Could you please diff your log with mine, to see if the problem was possibly caused by different build-dep versions ? I'm building on i386 as my amd64 boxes are currently still offline along with my hppa and alpha machines. The official amd64 buildd I sent the URL that was available for the log. When looking through it I didn't see any failures. However that log format and your log format are completely different and do not lend themselves to diff comparison. I'm talking about a build in an up-to-date sid chroot, not something that happened 10 days ago. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | signature.asc Description: Digital signature
Bug#562443: libgcgi: FTBFS: /bin/bash: line 11: automake-1.11: command not found
Lucas Nussbaum wrote: On 24/12/09 at 13:02 -0500, Jeremy T. Bouse wrote: Lucas Nussbaum wrote: On 24/12/09 at 12:04 -0500, Jeremy T. Bouse wrote: I suggest there might be something wrong with the amd64 build box you're using as the buildd report [1] shows that 0.9.5.dfsg-5 was built successfully Dec 12th. I've also re-downloaded the 0.9.5.dfsg-5 version from the mirrors and rebuilt under a pbuilder chroot and it built successfully as well. The -4 version of the package had a problem in the debian/rules that caused this behavior but it was fixed in the -5 release. Could you please diff your log with mine, to see if the problem was possibly caused by different build-dep versions ? I'm building on i386 as my amd64 boxes are currently still offline along with my hppa and alpha machines. The official amd64 buildd I sent the URL that was available for the log. When looking through it I didn't see any failures. However that log format and your log format are completely different and do not lend themselves to diff comparison. I'm talking about a build in an up-to-date sid chroot, not something that happened 10 days ago. Here's the build for me... The source is from the mirror using dget and not from the git repo [1] that it was originally built and submitted to the mirror from. Prior to the build I did a 'pbuilder update' for DIST=sid to ensure it was current. Jeremy [1] git://git.debian.org/collab-maint/libgcgi.git I: using fakeroot in build. I: Current time: Thu Dec 24 19:51:17 EST 2009 I: pbuilder-time-stamp: 1261702277 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/sid-i386-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /dev/pts filesystem I: policy-rc.d already exists I: Obtaining the cached apt archive contents I: Installing the build-deps - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: i386 Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder This package was created automatically by pbuilder and should Depends: debhelper (= 7), libssl-dev, dpatch dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'. Reading package lists... Building dependency tree... Reading state information... aptitude is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Selecting previously deselected package pbuilder-satisfydepends-dummy. (Reading database ... 11014 files and directories currently installed.) Unpacking pbuilder-satisfydepends-dummy (from .../pbuilder-satisfydepends-dummy.deb) ... dpkg: dependency problems prevent configuration of pbuilder-satisfydepends-dummy: pbuilder-satisfydepends-dummy depends on debhelper (= 7); however: Package debhelper is not installed. pbuilder-satisfydepends-dummy depends on libssl-dev; however: Package libssl-dev is not installed. pbuilder-satisfydepends-dummy depends on dpatch; however: Package dpatch is not installed. dpkg: error processing pbuilder-satisfydepends-dummy (--install): dependency problems - leaving unconfigured Errors were encountered while processing: pbuilder-satisfydepends-dummy Reading package lists... Building dependency tree... Reading state information... Initializing package states... Writing extended state information... The following NEW packages will be installed: bsdmainutils{a} debhelper{a} dpatch{a} file{a} gettext{a} gettext-base{a} groff-base{a} html2text{a} intltool-debian{a} libcroco3{a} libglib2.0-0{a} libmagic1{a} libpcre3{a} libssl-dev{a} libssl0.9.8{a} libxml2{a} man-db{a} po-debconf{a} zlib1g-dev{a} The following partially installed packages will be configured: pbuilder-satisfydepends-dummy 0 packages upgraded, 19 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/13.8MB of archives. After unpacking 38.5MB will be used. Writing extended state information... debconf: delaying package configuration, since apt-utils is not installed Selecting previously deselected package libmagic1. (Reading database ... 11014 files and directories currently installed.) Unpacking libmagic1 (from .../libmagic1_5.03-5_i386.deb) ... Selecting previously deselected package file. Unpacking file (from .../archives/file_5.03-5_i386.deb) ... Selecting previously deselected package html2text. Unpacking html2text (from .../html2text_1.3.2a-14_i386.deb) ... Selecting previously deselected package libpcre3. Unpacking libpcre3 (from .../libpcre3_7.8-3_i386.deb) ... Selecting previously deselected package libglib2.0-0. Unpacking libglib2.0-0 (from .../libglib2.0-0_2.22.3-2_i386.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from