Your message dated Mon, 10 Dec 2007 19:17:04 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#453207: fixed in gtkorphan 0.4.2-4
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: gtkorphan
version: 0.4.2-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20071126 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

Relevant part:

 > dh_testroot
 > dh_installchangelogs ChangeLog
 > dh_installdocs
 > dh_installexamples
 > dh_installmenu
 > dh_installman
 > dh_link
 > dh_strip
 > dh_compress
 > dh_fixperms
 > dh_perl
 > dh_installdeb
 > dh_shlibdeps
 > dh_gencontrol
 > dh_md5sums
 > dh_builddeb
 > dpkg-deb: parse error, in file `debian/gtkorphan/DEBIAN/control' near line 6 
 > package `gtkorphan':
 >  `Depends' field, syntax error after reference to package `deborphan'
 > dh_builddeb: command returned error code 512
 > make: *** [binary-indep] Error 1
 > dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave error 
 > exit status 2

The full build log is available from:
        http://people.debian.org/~lucas/logs/2007/11/26

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 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.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Source: gtkorphan
Source-Version: 0.4.2-4

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

gtkorphan_0.4.2-4.diff.gz
  to pool/main/g/gtkorphan/gtkorphan_0.4.2-4.diff.gz
gtkorphan_0.4.2-4.dsc
  to pool/main/g/gtkorphan/gtkorphan_0.4.2-4.dsc
gtkorphan_0.4.2-4_all.deb
  to pool/main/g/gtkorphan/gtkorphan_0.4.2-4_all.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.
Fabio Marzocca <[EMAIL PROTECTED]> (supplier of updated gtkorphan 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: Mon, 10 Dec 2007 17:40:47 +0100
Source: gtkorphan
Binary: gtkorphan
Architecture: source all
Version: 0.4.2-4
Distribution: unstable
Urgency: low
Maintainer: Fabio Marzocca <[EMAIL PROTECTED]>
Changed-By: Fabio Marzocca <[EMAIL PROTECTED]>
Description: 
 gtkorphan  - A graphical tool to find and remove orphaned libraries
Closes: 453207
Changes: 
 gtkorphan (0.4.2-4) unstable; urgency=low
 .
   * Closes:#453207
Files: 
 cd424372815a9617ca9bfaa4e0a53073 623 admin optional gtkorphan_0.4.2-4.dsc
 ba92a58213a53254bd72e2299702fa26 1959 admin optional gtkorphan_0.4.2-4.diff.gz
 07e1d788e18cfb62d2fc63f3150c2f8a 30384 admin optional gtkorphan_0.4.2-4_all.deb

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

iD8DBQFHXYwGvcCgrgZGjesRAq9gAJ0cVL+BKyQ4koWL3oBMaSEEs/3ilwCfRj3G
P4GPzj+zXI7vlNHR8B8n8FE=
=G+zB
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to