Your message dated Mon, 15 Aug 2005 14:47:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321251: fixed in libhoard 2.1.2d-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; 4 Aug 2005 12:35:17 +0000
>From [EMAIL PROTECTED] Thu Aug 04 05:35:17 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 1E0ewP-0007Yf-00; Thu, 04 Aug 2005 05:35:17 -0700
Received: from hades2.marenka.net (hades2.marenka.net [10.0.0.2])
        by hades.marenka.net (Postfix) with ESMTP id A771E1778F
        for <[EMAIL PROTECTED]>; Thu,  4 Aug 2005 07:35:16 -0500 (CDT)
Received: from localhost (hades2.marenka.net [127.0.0.1])
        by hades2.marenka.net (Postfix) with ESMTP id C51A535894
        for <[EMAIL PROTECTED]>; Thu,  4 Aug 2005 07:35:16 -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 03076-04 for <[EMAIL PROTECTED]>;
        Thu, 4 Aug 2005 07:35:12 -0500 (CDT)
Received: by hades2.marenka.net (Postfix, from userid 105)
        id C66F83583A; Thu,  4 Aug 2005 07:35:11 -0500 (CDT)
Received: by loki.marenka.net (Postfix, from userid 1000)
        id EB88A1308B7; Thu,  4 Aug 2005 07:32:02 -0500 (CDT)
Date: Thu, 4 Aug 2005 07:32:02 -0500
From: Stephen R Marenka <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: libhoard_2.1.2d-1(m68k/unstable/poseidon): 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: libhoard
Version: 2.1.2d-1
Severity: serious
Justification: fails to build on release candidate arch.
Tags: sid


libhoard 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
-O2 or gcc-3.3/gcc-3.4.


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

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

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

---------------------------------------
Received: (at 321251-close) by bugs.debian.org; 15 Aug 2005 21:49:53 +0000
>From [EMAIL PROTECTED] Mon Aug 15 14:49:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1E4mnf-0007bH-00; Mon, 15 Aug 2005 14:47:19 -0700
From: Adam Majer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#321251: fixed in libhoard 2.1.2d-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 15 Aug 2005 14:47:19 -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: libhoard
Source-Version: 2.1.2d-2

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

libhoard_2.1.2d-2.diff.gz
  to pool/main/libh/libhoard/libhoard_2.1.2d-2.diff.gz
libhoard_2.1.2d-2.dsc
  to pool/main/libh/libhoard/libhoard_2.1.2d-2.dsc
libhoard_2.1.2d-2_i386.deb
  to pool/main/libh/libhoard/libhoard_2.1.2d-2_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.
Adam Majer <[EMAIL PROTECTED]> (supplier of updated libhoard 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, 15 Aug 2005 16:36:18 -0500
Source: libhoard
Binary: libhoard
Architecture: source i386
Version: 2.1.2d-2
Distribution: unstable
Urgency: low
Maintainer: Adam Majer <[EMAIL PROTECTED]>
Changed-By: Adam Majer <[EMAIL PROTECTED]>
Description: 
 libhoard   - fast memory allocation library
Closes: 321251
Changes: 
 libhoard (2.1.2d-2) unstable; urgency=low
 .
   * Added a workaround for the problem with the m68k compiler and -O6
     optimizations by setting optimizations to -O2 on that architecture.
     (closes: #321251)
Files: 
 bd0def21355c19b7e79800fb23e70dca 561 libs optional libhoard_2.1.2d-2.dsc
 7d57f75da47de4a43a32aed96985ad1b 3853 libs optional libhoard_2.1.2d-2.diff.gz
 c4673b707a6458d1bff2c3e55bc5d1b1 35704 libs optional libhoard_2.1.2d-2_i386.deb

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

iD8DBQFDAQsf73/bNdaAYUURArJbAKDYFvxyBhsKGFezF+dGuQK+imCQiACgggWv
A0GACCEx1IY0XhJ9oi/z7l8=
=+FID
-----END PGP SIGNATURE-----


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

Reply via email to