Your message dated Thu, 15 Sep 2005 07:02:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#328453: fixed in pbzip2 0.9.4-2
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 15 Sep 2005 12:22:39 +0000
>From [EMAIL PROTECTED] Thu Sep 15 05:22:39 2005
Return-path: <[EMAIL PROTECTED]>
Received: from adsl-78-168-20.hsv.bellsouth.net (hades.marenka.net) 
[216.78.168.20] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EFslD-00026H-00; Thu, 15 Sep 2005 05:22:39 -0700
Received: from hades2.marenka.net (hades2.marenka.net [10.0.0.2])
        by hades.marenka.net (Postfix) with ESMTP id F37E11778F
        for <[EMAIL PROTECTED]>; Thu, 15 Sep 2005 07:22:37 -0500 (CDT)
Received: from localhost (hades2.marenka.net [127.0.0.1])
        by hades2.marenka.net (Postfix) with ESMTP id 34521358F4
        for <[EMAIL PROTECTED]>; Thu, 15 Sep 2005 07:22:38 -0500 (CDT)
Received: from hades2.marenka.net ([127.0.0.1])
        by localhost (hades2 [127.0.0.1]) (amavisd-new, port 10024)
        with ESMTP id 14748-04 for <[EMAIL PROTECTED]>;
        Thu, 15 Sep 2005 07:22:34 -0500 (CDT)
Received: by hades2.marenka.net (Postfix, from userid 10)
        id AA18835894; Thu, 15 Sep 2005 07:22:34 -0500 (CDT)
Received: by loki.marenka.net (Postfix, from userid 1000)
        id 04B65130365; Thu, 15 Sep 2005 07:22:25 -0500 (CDT)
Date: Thu, 15 Sep 2005 07:22:25 -0500
From: Stephen R Marenka <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: pbzip2_0.9.4-1(m68k/unstable/zeus): FTBFS on m68k
Message-ID: <[EMAIL PROTECTED]>
Mail-Followup-To: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at marenka.net
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: pbzip2
Version: 0.9.4-1
Severity: serious
Justification: fails to build on release candidate arch.
Tags: sid


pbzip2 fails to build from source on m68k. This is likely due
to bug #317475 on gcc-4.0. As a workaround, you might try compiling with
less optimization or gcc-3.3/gcc-3.4.


A full buildd log is available at 
<http://buildd.debian.org/build.php?pkg=pbzip2&ver=0.9.4-1&arch=m68k>

Other buildd logs may be available at 
<http://buildd.debian.org/build.php?arch=&pkg=pbzip2>

--
Stephen R. Marenka     If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>

---------------------------------------
Received: (at 328453-close) by bugs.debian.org; 15 Sep 2005 14:08:02 +0000
>From [EMAIL PROTECTED] Thu Sep 15 07:08:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EFuJW-0001el-00; Thu, 15 Sep 2005 07:02:10 -0700
From: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#328453: fixed in pbzip2 0.9.4-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 15 Sep 2005 07:02:10 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: pbzip2
Source-Version: 0.9.4-2

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

pbzip2_0.9.4-2.diff.gz
  to pool/main/p/pbzip2/pbzip2_0.9.4-2.diff.gz
pbzip2_0.9.4-2.dsc
  to pool/main/p/pbzip2/pbzip2_0.9.4-2.dsc
pbzip2_0.9.4-2_i386.deb
  to pool/main/p/pbzip2/pbzip2_0.9.4-2_i386.deb
pbzip2_0.9.4-2_sparc.deb
  to pool/main/p/pbzip2/pbzip2_0.9.4-2_sparc.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.
Anibal Monsalve Salazar <[EMAIL PROTECTED]> (supplier of updated pbzip2 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: Thu, 15 Sep 2005 23:38:32 +1000
Source: pbzip2
Binary: pbzip2
Architecture: source i386 sparc
Version: 0.9.4-2
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Changed-By: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Description: 
 pbzip2     - parallel bzip2 implementation
Closes: 328453
Changes: 
 pbzip2 (0.9.4-2) unstable; urgency=low
 .
   * debian/rules: no optimizacion for m68k, closes: #328453.
Files: 
 8f07ac2b33f194f0abdd24008ce814d3 578 utils optional pbzip2_0.9.4-2.dsc
 819987ed170d62e68ff3fa900fcb4ef1 2942 utils optional pbzip2_0.9.4-2.diff.gz
 cddbecd34821870023b6f9b9de6269bc 22918 utils optional pbzip2_0.9.4-2_i386.deb
 3ed65aced1f4942403f43fe3bbbbe1ba 23096 utils optional pbzip2_0.9.4-2_sparc.deb

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

iD8DBQFDKXzMgY5NIXPNpFURAplfAJ9txH100EUv736oUp4zq6K9vc4RUgCfUjNM
U95KjAvilyIXRDeEPAFlAHs=
=DN9W
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to