Your message dated Thu, 31 Mar 2005 16:17:09 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#295932: fixed in powermgmt-base 1.22
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; 19 Feb 2005 06:07:00 +0000
>From [EMAIL PROTECTED] Fri Feb 18 22:07:00 2005
Return-path: <[EMAIL PROTECTED]>
Received: from adsl-75-59.swiftdsl.com.au (taco.redellipse.net) [218.214.75.59] 
(postfix)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1D2Nlc-0008F0-00; Fri, 18 Feb 2005 22:07:00 -0800
Received: from lambrid.internal.redellipse.net 
(ppp205-190.lns1.syd3.internode.on.net [203.122.205.190])
        (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
        (Client CN "RedEllipse(Lambrid)", Issuer "RedEllipse/Synerger CA" 
(verified OK))
        by taco.redellipse.net (Postfix) with ESMTP id E59BAFF4B
        for <[EMAIL PROTECTED]>; Sat, 19 Feb 2005 17:06:17 +1100 (EST)
Received: by lambrid.internal.redellipse.net (Postfix, from userid 1000)
        id 38E5DCFB6D; Sat, 19 Feb 2005 17:06:06 +1100 (EST)
Subject: powermgmt-base: on_ac_power: should deal with incorrect info in
        /proc/pmu a little better
From: Pascal Hakim <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Sat, 19 Feb 2005 17:06:06 +1100
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.3 
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: powermgmt-base
Version: 1.21
Severity: wishlist

Recently on debian-powerpc, someone complained[1] that anacron wasn't
running as it thought it was on battery problem. benh pointed[2] out
this was due to having the CONFIG_PMAC_PBOOK option turned on, while the
computer was a G5.

It'd be nice if on_ac_power could notice that the number of batteries
present was 0, and hence say that the computer is most probably running
on ac power.

Cheers,

Pasc


[1]: http://lists.debian.org/debian-powerpc/2005/02/msg00410.html
[2]: http://lists.debian.org/debian-powerpc/2005/02/msg00438.html

---------------------------------------
Received: (at 295932-close) by bugs.debian.org; 31 Mar 2005 21:28:34 +0000
>From [EMAIL PROTECTED] Thu Mar 31 13:28:34 2005
Return-path: <[EMAIL PROTECTED]>
Received: from gluck.debian.org [192.25.206.10] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DH7DN-0006SO-00; Thu, 31 Mar 2005 13:28:34 -0800
Received: from newraff.debian.org [208.185.25.31] (mail)
        by gluck.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DH7DN-00016U-00; Thu, 31 Mar 2005 14:28:33 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DH72L-0002lq-00; Thu, 31 Mar 2005 16:17:09 -0500
From: Chris Hanson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#295932: fixed in powermgmt-base 1.22
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 31 Mar 2005 16:17:09 -0500
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-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
X-Spam-Level: 

Source: powermgmt-base
Source-Version: 1.22

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

powermgmt-base_1.22.dsc
  to pool/main/p/powermgmt-base/powermgmt-base_1.22.dsc
powermgmt-base_1.22.tar.gz
  to pool/main/p/powermgmt-base/powermgmt-base_1.22.tar.gz
powermgmt-base_1.22_i386.deb
  to pool/main/p/powermgmt-base/powermgmt-base_1.22_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.
Chris Hanson <[EMAIL PROTECTED]> (supplier of updated powermgmt-base 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, 31 Mar 2005 15:27:16 -0500
Source: powermgmt-base
Binary: powermgmt-base
Architecture: source i386
Version: 1.22
Distribution: unstable
Urgency: low
Maintainer: Chris Hanson <[EMAIL PROTECTED]>
Changed-By: Chris Hanson <[EMAIL PROTECTED]>
Description: 
 powermgmt-base - Common utils and configs for power management
Closes: 295932
Changes: 
 powermgmt-base (1.22) unstable; urgency=low
 .
   From Thom May <[EMAIL PROTECTED]>:
 .
   * Ensure on_ac_power works correctly on desktop G4/G5 systems.
     (closes: Bug#295932)
Files: 
 6898892728c59055911545eb4c0ab317 506 utils optional powermgmt-base_1.22.dsc
 d148f8b4902f9d4c97dd1fde4bc0d010 10995 utils optional 
powermgmt-base_1.22.tar.gz
 f093ff392684e1bc2cf43f3b831f072e 10408 utils optional 
powermgmt-base_1.22_i386.deb

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

iD8DBQFCTGPC46qC2Bs1LAERApOPAJ9zc7Qa0aCXFGnz/xYQk6phUuzEUwCaA5fA
BysBahty5I82YEDb4adhhh8=
=dTZE
-----END PGP SIGNATURE-----


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

Reply via email to