Your message dated Sun, 06 Apr 2008 23:17:07 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#442591: fixed in gtodo 0.16.0~rc2-1.1
has caused the Debian Bug report #442591,
regarding gtodo: FTBFS if build 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.)


-- 
442591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442591
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gtodo
Severity: important
Version: 0.16.0~rc2-1
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:


make[1]: Leaving directory `/build/user/gtodo-0.16.0~rc2'
 rm -f debian/stamp-makefile-build
 rm -f debian/stamp-autotools-files
 dh_clean 
 cd . && \
          rm -f intltool-extract intltool-merge intltool-update 
po/.intltool-merge-cache; \
          if test -d doc; then find doc -name '*.omf.out' -exec rm -f \{\} \; ; 
fi; \
          if test -d help; then find help -name '*.omf.out' -exec rm -f \{\} \; 
; fi
  dpkg-source -b gtodo-0.16.0~rc2
 dpkg-source: building gtodo using existing gtodo_0.16.0~rc2.orig.tar.gz
 dpkg-source: building gtodo in gtodo_0.16.0~rc2-1.diff.gz
 dpkg-source: cannot represent change to po/de.gmo: binary file contents changed
 dpkg-source: building gtodo in gtodo_0.16.0~rc2-1.dsc
 dpkg-source: unrepresentable changes to source
 ******************************************************************************
 Build finished at 20070906-0234
 #### END OF BUILD NO 2 ####
 FAILED [dpkg-buildpackage died]
 Purging 
/var/lib/schroot/mount/sid32-c0291927-c05b-401b-90c6-627b9f941ffb/build/user/gtodo-0.16.0~rc2
 ------------------------------------------------------------------------------
 Not removing build depends: session managed chroot in use
 ******************************************************************************
 Finished at 20070906-0234
 Build needed 00:00:21, 1644k disk space
 DC-Build-Status: Failed 358.124255s
 DC-Time-Estimation: 358.124255 versus expected 64 (r/m: 4.595691484375 ; m: 
64.0)
 mv: cannot stat `*.changes': No such file or directory
 mv: cannot stat `*.dsc': No such file or directory
 mv: cannot stat `*gz': No such file or directory
 mv: cannot stat `*deb': No such file or directory



The full build-log can be found at: 
http://people.debian.org/~lucas/logs/2007/doublebuild-09-05/failed-build-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.

Please read the mail of Martin Zobel-Helas on debian-devel [0], for a 
explanation 
for this mass bug filling.


[0]: http://lists.debian.org/debian-devel/2007/05/msg00490.html




--- End Message ---
--- Begin Message ---
Source: gtodo
Source-Version: 0.16.0~rc2-1.1

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

gtodo_0.16.0~rc2-1.1.diff.gz
  to pool/main/g/gtodo/gtodo_0.16.0~rc2-1.1.diff.gz
gtodo_0.16.0~rc2-1.1.dsc
  to pool/main/g/gtodo/gtodo_0.16.0~rc2-1.1.dsc
gtodo_0.16.0~rc2-1.1_i386.deb
  to pool/main/g/gtodo/gtodo_0.16.0~rc2-1.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.
Barry deFreese <[EMAIL PROTECTED]> (supplier of updated gtodo 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: Sun, 06 Apr 2008 16:38:37 -0400
Source: gtodo
Binary: gtodo
Architecture: source i386
Version: 0.16.0~rc2-1.1
Distribution: unstable
Urgency: high
Maintainer: Guilherme de S. Pastore <[EMAIL PROTECTED]>
Changed-By: Barry deFreese <[EMAIL PROTECTED]>
Description: 
 gtodo      - GNOME to-do list manager
Closes: 368249 442591 449725
Changes: 
 gtodo (0.16.0~rc2-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Fix clean to build twice. (Closes: #442591).
   * Add Swedish Translation. (Closes: #368249).
     + Thanks to Daniel Nylander for the translation.
   * Fix watch file. (Closes: #449725).
   * Move Homepage from package description to source header.
   * Add copyright holders to debian/copyright.
   * Update download URL in debian/copyright.
   * Bump debhelper build-dep and compat to 5.
   * Bump Standards Version to 3.7.3.
     + Menu policy transition.
Files: 
 8198f5d541ebb2ded317c5b624e234e6 759 x11 optional gtodo_0.16.0~rc2-1.1.dsc
 fb628b0cb913392d3275583fe28ca462 16053 x11 optional 
gtodo_0.16.0~rc2-1.1.diff.gz
 add971ad39073c591f2901b82ec2f683 100768 x11 optional 
gtodo_0.16.0~rc2-1.1_i386.deb

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

iEYEARECAAYFAkf5VesACgkQDb3UpmEybUATMwCfbxY/hRCARh1D4+AbJA/XUYCY
MncAn3dx+Q8uINfcOU22P1IEZETQILR4
=3C2z
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to