Your message dated Fri, 11 Mar 2016 09:51:41 +0000
with message-id <[email protected]>
and subject line Bug#484264: fixed in libacpi 0.2-4.1
has caused the Debian Bug report #484264,
regarding yacpi: always shows battery capacity at 0% in MacBook2,1
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
484264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484264
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: yacpi
Version: 3.0-2
Severity: important

Hi there,

Subject says it all: in any case yacpi shows BAT0 capacity at 0%,
so it's not very useful on my macbook version and probably others.

regards,

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages yacpi depends on:
ii  libacpi0                  0.2-4          general purpose library for ACPI
ii  libc6                     2.9-21         GNU C Library: Shared libraries
ii  libncurses5               5.7+20090613-1 shared libraries for terminal hand

yacpi recommends no packages.

yacpi suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: libacpi
Source-Version: 0.2-4.1

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

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.
Petter Reinholdtsen <[email protected]> (supplier of updated libacpi 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: SHA256

Format: 1.8
Date: Fri, 11 Mar 2016 09:37:08 +0100
Source: libacpi
Binary: libacpi-dev libacpi0
Architecture: source
Version: 0.2-4.1
Distribution: unstable
Urgency: low
Maintainer: Nico Golde <[email protected]>
Changed-By: Petter Reinholdtsen <[email protected]>
Description:
 libacpi-dev - development files for libacpi
 libacpi0   - general purpose library for ACPI
Closes: 479096 484264 701683 791969
Changes:
 libacpi (0.2-4.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Change source format to 3.0 (quilt).
   * Adjusted library to handle new file names in
     /sys/ (Closes: #479096, #484264).
   * Added simple autopkgtest to the package.  Patch from
     Vibhav Pant and Ubuntu (Closes: #701683).
   * Changed Standards-Version from 3.7.3 to 3.9.7.
   * Switched from debhelper 5 to 9.
   * Added 'arm64' to list of build architectures (Closes: #791969).
Checksums-Sha1:
 c27ca020f60df1ef40591cb2c1b5ad4295f4e35a 1807 libacpi_0.2-4.1.dsc
 1606983d414f8d7f608dd46a8ef2274fcfe7a68d 5564 libacpi_0.2-4.1.debian.tar.xz
Checksums-Sha256:
 f0b733bc45a70b4119e5313cfe461097bb7d37b3813c6f80c34f438ee2bce68c 1807 
libacpi_0.2-4.1.dsc
 1667ddca38efada1629f42e4889b624e3450e380458b06988e64adc7fa045b26 5564 
libacpi_0.2-4.1.debian.tar.xz
Files:
 3a35b3f27b9d1e3e5303cbb6829e1f68 1807 libs optional libacpi_0.2-4.1.dsc
 358695221790210a9dc8fb00f26489d5 5564 libs optional 
libacpi_0.2-4.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJW4oPzAAoJEIEoCqCHuvsOQroQAIGXrPLsekNGKarHjdSJIQCp
RSEC3Ov2Wo5FzMDEWrgY2UGzHN0tCjrbBQ5dNAzENh9RpI1VLZODLc9NXMRFVUhP
hBtcluDJo4w9Ki21/VJET0LR8Ra7LxXTt1DHUfyHpXGxK3HLPu0VQOUvJ9gQ4cza
RKLg7DUGvuG0CL1vj9HvTsX1aNiF/BZRzQby3ZMGvYWtyxBmtFBDaNHxoRg0bQLi
26Fw4M/6YIEuzSjkWDZai35zhDnQqPyE8tt/zCpEj2ndxBmkSZJ4OiWlXX/1tA7R
zJjpbFb3VKVwJ8dkvpYJJmpkPvc2L77Oh36EhGh8mt3oFJVmbJ16oRFcN9hPKk6P
rL1pQfO8BLZWwSgwrqxi8LugrhmgeAhYTLkbZLbUGpKtbVOCTTeuTOkUtvdh2mcA
915ycjsDu95MPmsQh4Tnhqelid685ID4Pyv9aBryJe+orBR1Icx6T1gpngOMzTi8
GsZgKricmW0hX0w5WoclY5Ez49dyWQY+JqcVYLHifXKTcIss/pdO82VRzCmpnShj
IOPipzb2jXFnrTNDLOB8i/EtVWOi4aIisSWzP3M0ZfEUbaG01gSm6tz+hyGCFK5K
2azPxtpGtpwBCdDb7AuZFlP496iTR7NCZS7IQBsOYd0RRBCTcl2KzbXipLMq+OLp
xGj4hyXK4fz8zNZnBOWJ
=vJu1
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to