Your message dated Fri, 04 Apr 2008 22:32:05 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424396: fixed in guile-pg 0.16-4.1
has caused the Debian Bug report #424396,
regarding guile-pg: FTBFS if built twice in a row
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.)


-- 
424396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424396
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: guile-pg
Severity: important
Version: 0.16-4
User: [EMAIL PROTECTED]
Usertags: qa-doublebuild

Hi,



Lucas Nussbaum has rebuilt the whole archive on i386 and your package
FTBFS if built twice in a row with the following error:

touch configure-stamp
dh_testdir
/usr/bin/make
make[1]: Entering directory `/build/user/guile-pg-0.16'
CPP="gcc -E" guile-snarf -o libpostgres.x libpostgres.c -DHAVE_CONFIG_H -I.  
-I/usr/include/postgresql  -g -O2 -Wall -Wmissing-prototypes
CPP="gcc -E" guile-snarf -o libpostgres_lo.x libpostgres_lo.c -DHAVE_CONFIG_H 
-I.  -I/usr/include/postgresql  -g -O2 -Wall -Wmissing-prototypes
/usr/bin/make  all-recursive
make[2]: Entering directory `/build/user/guile-pg-0.16'
Making all in scm
make[3]: Entering directory `/build/user/guile-pg-0.16/scm'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/build/user/guile-pg-0.16/scm'
Making all in test
make[3]: Entering directory `/build/user/guile-pg-0.16/test'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/build/user/guile-pg-0.16/test'
Making all in doc
make[3]: Entering directory `/build/user/guile-pg-0.16/doc'
/usr/bin/make  all-am
make[4]: Entering directory `/build/user/guile-pg-0.16/doc'
restore=: && backupdir=".am$$" && \
        rm -rf $backupdir && mkdir $backupdir && \
        if (/bin/sh /build/user/guile-pg-0.16/missing --run makeinfo --version) 
>/dev/null 2>&1; then \
          for f in guile-pg.info guile-pg.info-[0-9] guile-pg.info-[0-9][0-9] 
guile-pg.i[0-9] guile-pg.i[0-9][0-9]; do \
            if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
          done; \
        else :; fi && \
        if /bin/sh /build/user/guile-pg-0.16/missing --run makeinfo   -I . \
         -o guile-pg.info `test -f 'guile-pg.texi' || echo './'`guile-pg.texi; \
        then \
          rc=0; \
        else \
          rc=$?; \
          $restore $backupdir/* `echo "./guile-pg.info" | sed 's|[^/]*$||'`; \
        fi; \
        rm -rf $backupdir; exit $rc
/build/user/guile-pg-0.16/missing: line 52: makeinfo: command not found
WARNING: `makeinfo' is missing on your system.  You should only need it if
         you modified a `.texi' or `.texinfo' file, or any other file
         indirectly affecting the aspect of the manual.  The spurious
         call might also be the consequence of using a buggy `make' (AIX,
         DU, IRIX).  You might want to install the `Texinfo' package or
         the `GNU make' package.  Grab either from any GNU archive site.
make[4]: *** [guile-pg.info] Error 1
make[4]: Leaving directory `/build/user/guile-pg-0.16/doc'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/build/user/guile-pg-0.16/doc'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/user/guile-pg-0.16'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/user/guile-pg-0.16'
make: *** [build-stamp] Error 2


The full build-log can be found at:
http://people.debian.org/~lucas/logs/2007/05/15/00_Failed_2/


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. All
packages have been rebuilt twice in a row, with unpack, build, clean,
build.





--- End Message ---
--- Begin Message ---
Source: guile-pg
Source-Version: 0.16-4.1

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

guile-pg_0.16-4.1.diff.gz
  to pool/main/g/guile-pg/guile-pg_0.16-4.1.diff.gz
guile-pg_0.16-4.1.dsc
  to pool/main/g/guile-pg/guile-pg_0.16-4.1.dsc
guile-pg_0.16-4.1_i386.deb
  to pool/main/g/guile-pg/guile-pg_0.16-4.1_i386.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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi <[EMAIL PROTECTED]> (supplier of updated guile-pg 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: Wed, 02 Apr 2008 09:18:54 +0200
Source: guile-pg
Binary: guile-pg
Architecture: source i386
Version: 0.16-4.1
Distribution: unstable
Urgency: low
Maintainer: Sam Hocevar (Debian packages) <[EMAIL PROTECTED]>
Changed-By: Sandro Tosi <[EMAIL PROTECTED]>
Description: 
 guile-pg   - Guile bindings for the PostgreSQL client library
Closes: 424396
Changes: 
 guile-pg (0.16-4.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/control:
     + Added texinfo build-depends to fix a FTBFS (Closes: #424396).
Files: 
 10441a72c1e240894a8e8ff39aa79869 622 interpreters optional 
guile-pg_0.16-4.1.dsc
 e084534854b0aea74c008f3fbd4f27dd 440566 interpreters optional 
guile-pg_0.16-4.1.diff.gz
 8922518b2ece5a5f9ac2754a62b265e5 79116 interpreters optional 
guile-pg_0.16-4.1_i386.deb

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

iD8DBQFH9qSATTx8oVVPtMYRAhi7AKC9KRo7Y8y8nVkwxBBEfyxYDQRsowCgwr+t
Ea04kv4n+TaRDMbcUL5UJGk=
=L5wK
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to