Today a 2.0 beta release of cpufreq was released. Significant changes happend from the 1.X tree. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 66903 [details, diff] 1.2.3-2.0.0 patch Attached is the diff patch to allow you to install 2.0 beta4. Notice the new dependency on cpufrequtils as well the warning about significant changes to the /etc/cpufreqd.conf file. Would a ewarn be better in this case?
Created attachment 66904 [details, diff] doh forgot to remove the cvs header part X_X
You also missed a few other issues (such as KEYWORDS and the fact that cpufreqd-2.0.0-beta4 doesn't include the gentoo init script). I have re-written the ebuild and the init script from scratch and added them to portage. Thank you for reporting this.
There is an inconsistency with the cpu plugin's keyword between the beta4 source code, where it is coded as "cpu", and the man page and the default configuration file, where it is described as "cpu_interval". I don't know which way the author wants to go, but as it is, this beta version of cpufreqd will appear crippled to many users.
Please report that upstream.
Created attachment 67185 [details, diff] diff just applied to cpufreqd2 CVS I'm going with the "cpu_interval-everywhere" solution. I won't release a beta5 in the next few days, so I attached the patch for your reference if you wish to apply it via emerge
Comment on attachment 67185 [details, diff] diff just applied to cpufreqd2 CVS oops, typo..., recreating the attachment
Created attachment 67186 [details, diff] the correct version
Thanks.
Fixed in sys-power/cpufreqd-2.0.0_beta4-r1. Thanks. Next time, please open a seperate bug report.
