Your message dated Sat, 29 Sep 2007 20:47:24 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#443022: fixed in ttf-staypuft 0.04-2.1
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: ttf-staypuft
version: 0.04-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20070917 qa-ftbfs
Justification: FTBFS on i386

Hi,

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

Relevant part:
dpkg-source: building ttf-staypuft in ttf-staypuft_0.04-2.dsc
 debian/rules build
dh_testdir
chmod 755 /build/user/ttf-staypuft-0.04/debian/ConvertFont
/build/user/ttf-staypuft-0.04/debian/ConvertFont StayPuft.sfd
Copyright (c) 2000-2007 by George Williams.
 Executable based on sources from 15:43 31-Aug-2007.
  File "/build/user/ttf-staypuft-0.04/debian/ConvertFont", line 6
    if ($argc > 1)
        ^
SyntaxError: invalid syntax
make: *** [build-stamp] Error 1

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

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: ttf-staypuft
Source-Version: 0.04-2.1

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

ttf-staypuft_0.04-2.1.diff.gz
  to pool/main/t/ttf-staypuft/ttf-staypuft_0.04-2.1.diff.gz
ttf-staypuft_0.04-2.1.dsc
  to pool/main/t/ttf-staypuft/ttf-staypuft_0.04-2.1.dsc
ttf-staypuft_0.04-2.1_all.deb
  to pool/main/t/ttf-staypuft/ttf-staypuft_0.04-2.1_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.
Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]> (supplier of updated 
ttf-staypuft 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: Sat, 29 Sep 2007 18:02:33 +0200
Source: ttf-staypuft
Binary: ttf-staypuft
Architecture: source all
Version: 0.04-2.1
Distribution: unstable
Urgency: low
Maintainer: Carlos Perelló Marín <[EMAIL PROTECTED]>
Changed-By: Ana Beatriz Guerrero Lopez <[EMAIL PROTECTED]>
Description: 
 ttf-staypuft - The Stay-Puft free TrueType font
Closes: 443022
Changes: 
 ttf-staypuft (0.04-2.1) unstable; urgency=low
 .
   * Non-maintainer upload to fix RC bug.
   * Add extension .ff to the script ConvertFont name, adapting it to the new
     fontforge version. (Closes: #443022)
Files: 
 a3b75c1d6dda8e074fb39c2c124cdb6e 653 x11 optional ttf-staypuft_0.04-2.1.dsc
 2c993a30b22a4b38e5e264c5f4fb2c2d 7125 x11 optional 
ttf-staypuft_0.04-2.1.diff.gz
 0edfc08a8d443de91cdd925e66f8c6bd 24468 x11 optional 
ttf-staypuft_0.04-2.1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Signed by Ana Guerrero

iD8DBQFG/q0Wn3j4POjENGERAneCAJ4qiEop4TrBJuiadB9uN57HPtIjhwCdHKPB
scJS2d7gQomyFQrx9i0lgV8=
=uFe6
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to