Your message dated Fri, 02 Sep 2005 09:47:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326224: fixed in kmldonkey 0.10-3
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; 2 Sep 2005 14:25:17 +0000
>From [EMAIL PROTECTED] Fri Sep 02 07:25: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 1EBCTl-0002gr-00; Fri, 02 Sep 2005 07:25:17 -0700
Received: from hades2.marenka.net (hades2.marenka.net [10.0.0.2])
        by hades.marenka.net (Postfix) with ESMTP id BA6C41778E
        for <[EMAIL PROTECTED]>; Fri,  2 Sep 2005 09:25:15 -0500 (CDT)
Received: from localhost (hades2.marenka.net [127.0.0.1])
        by hades2.marenka.net (Postfix) with ESMTP id EB06B36130
        for <[EMAIL PROTECTED]>; Fri,  2 Sep 2005 09:25:21 -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 01256-10 for <[EMAIL PROTECTED]>;
        Fri, 2 Sep 2005 09:25:18 -0500 (CDT)
Received: by hades2.marenka.net (Postfix, from userid 105)
        id C97A936196; Fri,  2 Sep 2005 09:25:17 -0500 (CDT)
Received: by loki.marenka.net (Postfix, from userid 1000)
        id 0C4131303B6; Fri,  2 Sep 2005 09:24:33 -0500 (CDT)
Date: Fri, 2 Sep 2005 09:24:33 -0500
From: Stephen R Marenka <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: kmldonkey_0.10-2(m68k/unstable/poseidon): fails to build from source
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: kmldonkey
Version: 0.10-2
Severity: serious
Justification: fails to build on release candidate arch.
Tags: sid


kmldonkey fails to build from source on m68k. You've likely been bit by
bug# 323133. One workaround would seem to be described in
<http://lists.debian.org/debian-devel-announce/2005/09/msg00000.html>.


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

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

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

---------------------------------------
Received: (at 326224-close) by bugs.debian.org; 2 Sep 2005 16:49:28 +0000
>From [EMAIL PROTECTED] Fri Sep 02 09:49:28 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EBEgz-0001CK-00; Fri, 02 Sep 2005 09:47:05 -0700
From: Peter Eisentraut <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#326224: fixed in kmldonkey 0.10-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 02 Sep 2005 09:47:05 -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: kmldonkey
Source-Version: 0.10-3

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

kmldonkey_0.10-3.diff.gz
  to pool/main/k/kmldonkey/kmldonkey_0.10-3.diff.gz
kmldonkey_0.10-3.dsc
  to pool/main/k/kmldonkey/kmldonkey_0.10-3.dsc
kmldonkey_0.10-3_i386.deb
  to pool/main/k/kmldonkey/kmldonkey_0.10-3_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.
Peter Eisentraut <[EMAIL PROTECTED]> (supplier of updated kmldonkey 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,  2 Sep 2005 18:02:16 +0200
Source: kmldonkey
Binary: kmldonkey
Architecture: source i386
Version: 0.10-3
Distribution: unstable
Urgency: low
Maintainer: Peter Eisentraut <[EMAIL PROTECTED]>
Changed-By: Peter Eisentraut <[EMAIL PROTECTED]>
Description: 
 kmldonkey  - KDE GUI for MLDonkey
Closes: 326224
Changes: 
 kmldonkey (0.10-3) unstable; urgency=low
 .
   * Rebuilt with GCC 3.4 on arm, m68k, hppa (closes: #326224)
Files: 
 3d735a25e11265f9ed9bd6fe3787c66f 654 net optional kmldonkey_0.10-3.dsc
 66505fd333f2c3104652f45d516cd1ca 2076 net optional kmldonkey_0.10-3.diff.gz
 7a815ea2b872c63e951f22238e56f772 924334 net optional kmldonkey_0.10-3_i386.deb

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

iD8DBQFDGH7UTTx8oVVPtMYRAlpfAKDFp3mYqoQl31nMTIf5/jGlyXGTsgCgnZAW
GPELgQi3Vke2w2nysJdggCo=
=QKBy
-----END PGP SIGNATURE-----


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

Reply via email to