merge 610816 598116 severity 610816 important retitle 610816 [libsensors3 removal] wmtemp: please switch to libsensors4 tag 610816 + patch thanks
On Sat, Jan 22, 2011 at 02:17:35PM -0600, hugo vanwoerkom wrote: > Package: wmtemp > Version: 0.0.6-3 > Severity: wishlist > > > I have an M4N98TD EVO Asus motherboard. When I use wmtemp with that it finds > no sensors. But 'sensors' reports: > > atk0110-acpi-0 > Adapter: ACPI interface > Vcore Voltage: +1.39 V (min = +0.80 V, max = +1.80 V) > 3.3V Voltage: +3.26 V (min = +2.97 V, max = +3.63 V) > 5V Voltage: +5.00 V (min = +4.50 V, max = +5.50 V) > 12V Voltage: +11.90 V (min = +10.20 V, max = +13.80 V) > CPU FAN Speed: 1406 RPM (min = 600 RPM) > CHASSIS1 FAN Speed: 0 RPM (min = 600 RPM) > CHASSIS2 FAN Speed: 0 RPM (min = 600 RPM) > CPU Temperature: +32.0°C (high = +60.0°C, crit = +75.0°C) > MB Temperature: +27.0°C (high = +45.0°C, crit = +75.0°C) > > and so does 'xsensors'. The difference appears to be installing and using > libsensors4 and libsensors4-dev. > So I patched wmtemp to do so and now it reports CPU and MB temps. I attach > the patch. > Indeed libsensors3 is now deprecated and is missing a lot of features, including the ability to read ACPI values. There are only 3 packages depending on libsensors3 (3 wmaker applets!), so it's probably time to get rid of this library which is deprecated for a few years. I will ask to the removal of this libsensors3 in about one month. That's why I am changing the severity to important. The patch attached to this bug report is correct (beside a strange patch level) and should be applied as soon as possible. Thanks in advance, Aurelien -- Aurelien Jarno GPG: 1024D/F1BCDB73 [email protected] http://www.aurel32.net -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
