When trying to emerge this latest version, I get an error. Reproducible: Always The error message suggested running portageq owners / /usr/share/hal (if I understood correctly). This give the following collisions sys-apps/hal-0.5.12_rc1 /usr/share/hal app-misc/hal-info-20090414 /usr/share/hal media-libs/libgphoto2-2.4.4 /usr/share/hal
At very least, paste the full error.
The full error message ========== >>> Installing sys-apps/hal-0.5.12_rc1-r1 * checking 180 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * Detected file collision(s): * * /usr/share/PolicyKit/policy/org.freedesktop.hal.power-management.policy * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * gnome-extra/gnome-power-manager-2.24.4-r1 * /usr/share/PolicyKit/policy/org.freedesktop.hal.power-management.policy * * Package 'sys-apps/hal-0.5.12_rc1-r1' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. >>> Failed to install sys-apps/hal-0.5.12_rc1-r1, Log file: >>> '/var/tmp/portage/sys-apps/hal-0.5.12_rc1-r1/temp/build.log' This log file had no useful information about the error.
I diffed both versions of the file and to me it looks like the hal version should be kept and gnome-power-manager should not install its own version. Reassigned to the gnome team. Denis.
this file was added to g-p-m back in the days when we needed a policy file for pk support in g-p-m but we didn't have pk support in hal
This is fixed.
*** Bug 268234 has been marked as a duplicate of this bug. ***
*** Bug 268243 has been marked as a duplicate of this bug. ***
*** Bug 268287 has been marked as a duplicate of this bug. ***
Problem is not fixed in sys-apps/hal-0.5.12_rc1-r2
This is not a hal problem; it's a gnome-power-manager problem. Re-emerge g-p-m.
(I hadn't realized 2.24.x had the problem too. It's fixed now, and a blocker added to hal)
(In reply to comment #10) > This is not a hal problem; it's a gnome-power-manager problem. Re-emerge > g-p-m. > I can't since g-p-m requires hal to be compiled :)
if g-p-m is not emerged, you cannot have a collision with hal. re-emerge g-p-m, and hal will update fine. The blocker resolves itself if you emerge -auvDN world.
(In reply to comment #13) > if g-p-m is not emerged, you cannot have a collision with hal. re-emerge > g-p-m, and hal will update fine. The blocker resolves itself if you emerge > -auvDN world. > Portage emerge hal first, then g-p-m :(
emerge -1 --nodeps gnome-power-manager
*** Bug 268833 has been marked as a duplicate of this bug. ***
