Your message dated Mon, 12 Sep 2005 18:47:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#327787: fixed in bubblemon 2.0.4-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; 12 Sep 2005 08:07:21 +0000
>From [EMAIL PROTECTED] Mon Sep 12 01:07:21 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (tennyson.dodds.net) 
[66.93.39.86] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EEjLV-0008N2-00; Mon, 12 Sep 2005 01:07:21 -0700
Received: by tennyson.dodds.net (Postfix, from userid 1000)
        id 8DD6F7038; Mon, 12 Sep 2005 01:07:20 -0700 (PDT)
Date: Mon, 12 Sep 2005 01:07:20 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: bubblemon: depends on libgtop2-2 on alpha, mips, mipsel
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="GxcwvYAGnODwn7V8"
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
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


--GxcwvYAGnODwn7V8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: bubblemon
Version: 2.0.4-2
Severity: grave

The latest version of bubblemon was uploaded in the middle of an ABI
transition for libgtop2, which means that the bubblemon package depends
on libgtop2-5 on 8 of 11 architectures, and on libgtop2-2 on alpha,
mips, and mipsel.  This makes the package uninstallable in sid on those
architectures, and at the moment prevents the GNOME 2.10 transition from
finishing.

Please arrange for fixed binary packages to enter the archive on these
architectures, either through a sourceful upload or through binNMUs on
the architectures in question.

Thanks,
--=20
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

--GxcwvYAGnODwn7V8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFDJTc4KN6ufymYLloRAoZ9AJ9wBnw85uB2c8FKJBx4EY4OIbJ9pgCfa1VS
OH1N4P0G6+sv9kZjvWQLgB4=
=zCF5
-----END PGP SIGNATURE-----

--GxcwvYAGnODwn7V8--

---------------------------------------
Received: (at 327787-close) by bugs.debian.org; 13 Sep 2005 01:48:37 +0000
>From [EMAIL PROTECTED] Mon Sep 12 18:48:37 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EEzt3-0007Np-00; Mon, 12 Sep 2005 18:47:05 -0700
From: Eric Dorland <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#327787: fixed in bubblemon 2.0.4-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 12 Sep 2005 18: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: bubblemon
Source-Version: 2.0.4-3

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

bubblemon_2.0.4-3.diff.gz
  to pool/main/b/bubblemon/bubblemon_2.0.4-3.diff.gz
bubblemon_2.0.4-3.dsc
  to pool/main/b/bubblemon/bubblemon_2.0.4-3.dsc
bubblemon_2.0.4-3_i386.deb
  to pool/main/b/bubblemon/bubblemon_2.0.4-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.
Eric Dorland <[EMAIL PROTECTED]> (supplier of updated bubblemon 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, 13 Jun 2005 01:05:39 -0400
Source: bubblemon
Binary: bubblemon
Architecture: source i386
Version: 2.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Eric Dorland <[EMAIL PROTECTED]>
Changed-By: Eric Dorland <[EMAIL PROTECTED]>
Description: 
 bubblemon  - Bubbling Load Monitoring GNOME Applet
Closes: 327787
Changes: 
 bubblemon (2.0.4-3) unstable; urgency=medium
 .
   * debian/control:
     - Bump Standards-Version to 3.6.2.1.
     - Build-Depend on newer libgtop to help out GNOME
       transition. (Closes: #327787)
Files: 
 7a02eb442f314032d0af294f05685a6b 688 gnome optional bubblemon_2.0.4-3.dsc
 88d90fde798639ccf6d12684721b5c68 3698 gnome optional bubblemon_2.0.4-3.diff.gz
 8994eb02db81407422f82c6bee19d6bd 36010 gnome optional 
bubblemon_2.0.4-3_i386.deb

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

iD8DBQFDJizUYemOzxbZcMYRAtpwAJkB10yFkwcOWUp5tQHv98/HfhLyzwCeMPxC
8SsSI0q7JbLou2OKwecIQQ8=
=Upal
-----END PGP SIGNATURE-----


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

Reply via email to