Your message dated Sat, 01 Oct 2005 03:47:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321953: fixed in ibam 1:0.3-7
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; 8 Aug 2005 12:55:18 +0000
>From [EMAIL PROTECTED] Mon Aug 08 05:55:18 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 1E279y-0003hH-00; Mon, 08 Aug 2005 05:55:18 -0700
Received: from hades2.marenka.net (hades2.marenka.net [10.0.0.2])
        by hades.marenka.net (Postfix) with ESMTP id BA1B51778E
        for <[EMAIL PROTECTED]>; Mon,  8 Aug 2005 07:55:16 -0500 (CDT)
Received: from localhost (hades2.marenka.net [127.0.0.1])
        by hades2.marenka.net (Postfix) with ESMTP id C9BEC35894
        for <[EMAIL PROTECTED]>; Mon,  8 Aug 2005 07:55: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 25969-07 for <[EMAIL PROTECTED]>;
        Mon, 8 Aug 2005 07:55:13 -0500 (CDT)
Received: by hades2.marenka.net (Postfix, from userid 105)
        id 561BD359C9; Mon,  8 Aug 2005 07:55:10 -0500 (CDT)
Received: by loki.marenka.net (Postfix, from userid 1000)
        id 2CC681308B8; Mon,  8 Aug 2005 07:53:39 -0500 (CDT)
Date: Mon, 8 Aug 2005 07:53:39 -0500
From: Stephen R Marenka <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: ibam_1:0.3-5(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: ibam
Version: 1:0.3-5
Severity: serious
Justification: fails to build on release candidate arch.
Tags: sid


ibam 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=ibam&ver=1:0.3-5&arch=m68k>

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

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

---------------------------------------
Received: (at 321953-close) by bugs.debian.org; 1 Oct 2005 10:51:31 +0000
>From [EMAIL PROTECTED] Sat Oct 01 03:51:31 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1ELetU-0004Yo-00; Sat, 01 Oct 2005 03:47:04 -0700
From: Martin Wuertele <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#321953: fixed in ibam 1:0.3-7
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 01 Oct 2005 03:47:04 -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: ibam
Source-Version: 1:0.3-7

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

gkrellm-ibam_0.3-7_m68k.deb
  to pool/main/i/ibam/gkrellm-ibam_0.3-7_m68k.deb
ibam_0.3-7.diff.gz
  to pool/main/i/ibam/ibam_0.3-7.diff.gz
ibam_0.3-7.dsc
  to pool/main/i/ibam/ibam_0.3-7.dsc
ibam_0.3-7_m68k.deb
  to pool/main/i/ibam/ibam_0.3-7_m68k.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.
Martin Wuertele <[EMAIL PROTECTED]> (supplier of updated ibam 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: Fri, 30 Sep 2005 19:06:36 +0200
Source: ibam
Binary: ibam gkrellm-ibam
Architecture: source m68k
Version: 1:0.3-7
Distribution: unstable
Urgency: low
Maintainer: Martin Wuertele <[EMAIL PROTECTED]>
Changed-By: Martin Wuertele <[EMAIL PROTECTED]>
Description: 
 gkrellm-ibam - Advanced battery monitor for laptops - gkrellm plugin
 ibam       - Advanced battery monitor for laptops
Closes: 321953
Changes: 
 ibam (1:0.3-7) unstable; urgency=low
 .
   * updated CFLAGS to prevent FTBFS on m68k
     (Closes: #321953)
Files: 
 bcdbdf305acbf45d3dedb47ffd769612 643 utils optional ibam_0.3-7.dsc
 f26d5e4aee4650d462e3c3b8e466ade1 7759 utils optional ibam_0.3-7.diff.gz
 a448d08413230162f8a5a22652ecc26a 29528 utils optional ibam_0.3-7_m68k.deb
 b6a46ca005a0a8104f27f192da7b747e 17372 x11 optional gkrellm-ibam_0.3-7_m68k.deb

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

iD8DBQFDPmWYKO6zWj6NzMARAuEGAJ9UOGfNgiGCnX8cXbp6FLap8Hi23ACdEoRu
FX1to7nhe2CPFtW2ASN6XsM=
=23yZ
-----END PGP SIGNATURE-----


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

Reply via email to