This bug was fixed in the package cpufreqd - 2.4.2-1
--------------- cpufreqd (2.4.2-1) unstable; urgency=low
* New upstream release: fixes configuration with libsensors4 (Closes: #577822).
cpufreqd (2.4.1-1) unstable; urgency=low
* New upstream release (Closes: #547483), now supports libsensors4 (Closes: #454617) and ignores ignored features (Closes: #538950). * Switch to dpkg-source 3.0 (quilt) format (Closes: #538546). * Remove patch merged upstream -- Artur Rona <email address hidden> Sun, 18 Apr 2010 23:08:30 +0900
This bug was fixed in the package cpufreqd - 2.4.2-1
---------------
cpufreqd (2.4.2-1) unstable; urgency=low
* New upstream release: fixes configuration with libsensors4
(Closes: #577822).
cpufreqd (2.4.1-1) unstable; urgency=low
* New upstream release (Closes: #547483), now supports libsensors4
(Closes: #454617) and ignores ignored features (Closes: #538950).
* Switch to dpkg-source 3.0 (quilt) format (Closes: #538546).
* Remove patch merged upstream
-- Artur Rona <email address hidden> Sun, 18 Apr 2010 23:08:30 +0900