Guys, we need this stable with for gnome-power-manager-2.24*, OK to stabilize this version? (0.5.13 needs newer util-linux). I'll CC arches once I get an OK.
So people have expressed a desire to see newer util-linux go stable, hence we can stabilize 0.5.13-r2 (which has lots of bugfixes iirc)
I'm good with 0.5.13-r2 going stable as soon as util-linux is stable. It certainly fixes tons of stuff.
OK, it seems util-linux-2.16 isn't going stable just yet, let's aim for hal-0.5.12_rc1-r7 Arches, please stabilize, you need this for gnome-2.26 @amd64+x86: magic word "10.0" :)
No magic here yet, we need to figure out relationship with gnome-power-manager (policy file migration and blockers) and see what revisions of each to go with. Un-CC'ing until this is decided, sorry for the noise
Ok, we can actually just proceed with hal-0.5.12_rc1-r7 because the policykit file in question isn't shipped by current stable gnome-power-manager anyhow, because 2.22 series had policykit support disabled. And once we stable 2.24 in the very near term future, it won't be shipping the policykit file either, as all those revisions that did are gone by now. Some arches might need to do bug 278181 before they can get this newer hal without keyword visibility problems, so marking as a dependent bug. Please stabilize: sys-apps/hal-0.5.12_rc1-r7 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86
amd64 done
(In reply to comment #6) > amd64 done Does somebody care for stabilizing >=gnome-power-manaber-2.24.4-r2 as well? Because the new hal block any lower version.
gnome-power-manager-2.24 doesn't seem so well working for me, it's causing serious brightness related problems on my laptop for example, so it's staying at 2.22 for now. That said, I did screw up regarding the blocker, which was initially meant only for earlier gnome-power-manager-2.24 versions that shipped a policy file with USE=policykit. But the block covered 2.22 too, so I've removed it now from all HAL versions and made a hal-0.5.12_rc1-r8 as well to get all amd64 users to get the blocker record removed from VDB records as well, with an OK from amd64 team member mrpouet. Other arches: Please stabilize hal-0.5.12_rc1-r8 revision instead of the previous request to be in sync with amd64 last stable (r7 and r8 are at present time equal besides whitespace)
(In reply to comment #8) > gnome-power-manager-2.24 doesn't seem so well working for me, it's causing > serious brightness related problems on my laptop for example, so it's staying > at 2.22 for now. Ubuntu seems to be applying some patches that could help on this, have you look at them?
No, I could do so later though, once GNOME-2.26 is stable. Just no time to deal with it now without delaying 2.26 even longer
Apparently, this misses a dep on libvolume_id: checking for gperf... /usr/bin/gperf checking whether to rebuild gperf header files... checking for DBUS... yes checking for GLIB... yes checking if GLib is version 2.14.0 or newer... yes checking for VOLUME_ID... configure: error: Package requirements (libvolume_id >= 0.77) were not met: No package 'libvolume_id' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables VOLUME_ID_CFLAGS and VOLUME_ID_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. --- Also note that libvolume_id is not keyworded on alpha.
x86 stable
*** This bug has been marked as a duplicate of bug 287380 ***
