[19:55] <OvenWerks> for any who care.... https://code.launchpad.net/~ubuntustudio-dev/ubuntustudio-controls/trunk could be uploaded as there is a new commit.
[19:58] <OvenWerks> ubuntustudio-controls can now set the cpu governor to performance or powersave. This is not something that stays set across boots. Right now there is a bug in sysvinit (bug #1646245) that will not allow cpufreq to do it's job.
[20:12] <OvenWerks> If you would like to try out this new version of -controls it is available from https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild
[20:13]  * OvenWerks goes off to try it on 32bit machine just in case.
[21:02] <OvenWerks> Well it works fine on 32bit machines too (surprise, surprise) I am now wondering why the 32 bit kernel has more available governors than the 64bit kernel... Or maybe it is my machine.
[21:03] <OvenWerks> Anyway, both have powersave and performance available and that is what I switch between. I have heard that ondemand actually uses more power than performance, so powersave may be better.
[21:05] <OvenWerks> krytarik: I think I may remove the fix in -settings (rollback the commit) because of the bug in /etc/init.d/ondemand which keeps it from working.
[21:07] <OvenWerks> If that gets fixed I can add it back as well as a checkbox in -controls "Make this setting default".
[21:09] <OvenWerks> I am really not sure how it might get fixed. I would like to see it get removed, but that would make cpu-freq a required package, so it may make more sense to change ondemand to check /etc/defaults for /etc/default/ondemand which can have the default governor on a line.
[21:10] <OvenWerks> Anyone who cares to confirm bug #1646245 might help.
[21:27] <OvenWerks> dch
[21:27] <OvenWerks> ... wrong window...
[21:32] <OvenWerks> krytarik: fixed the changelog in -setting and removed the cpugovernor commit both.
[21:33] <OvenWerks> krytarik: I am guessing it needs to be uploaded now. (along with -controls)
[21:46] <krytarik> OvenWerks: Thanks.  However, 1.) now you merged your changes with Ross'; 2.) "* Undo last commit because bug 1646245 won't let it work" - you dropped that commit completely from the history; and 3.) I don't think something like "* Fix changelog version." or "* Fix changelog" needs to be in the changelog itself, as long as it wasn't released since.
[21:51] <krytarik> ..And not to mention the dire uploader situation currently. >_>
[21:52] <OvenWerks> I assume we don't have any?
[21:52] <OvenWerks> (uploader)
[21:55] <OvenWerks> Not sure which way to go on that.
[21:56] <OvenWerks> (either the upload thing or fixing settings without making it worse)
[21:57] <OvenWerks> But if there is no way to upload aything, "we may as well go home"
[22:00] <krytarik> Well, we can try and let people who do have upload rights sponser things, as we did at the end of last cycle, after Kaj took off - but of course, that's rather impractical in the long run.
[22:01]  * OvenWerks has to run, gotta pick up my wife.
[22:03] <krytarik> And well, just do as you did before apparently - undo things and force-push. >_>
[23:36] <krytarik> OvenWerks: Btw, feel free to enable the autobuilds for the relevant sources once you think the changes in them are worth it yet - but then I'd switch to '{debupstream}+bzr{revno}+{time}' for the versioning.
[23:37] <krytarik> ..Oh, I mean for the Yakkety and Zesty series more specifically.