emerge -NuD world, hal upgrades to 0.5, dbus to 0.60. do it again: emerge -NuDp world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild UD] sys-apps/dbus-0.23.4-r1 [0.60-r3] [ebuild UD] sys-apps/hal-0.4.8 [0.5.5.1-r3] which sort of causes and emerge infinite loop since the next emerge will try to upgrade hal/dbus again.
Are you perhaps using ivman (stable version)? - ivman-0.5_pre2 wants hal-0.4* (thus hal-0.4.8), wich wants dbus-0.23 The fact is that the last *stable* versions of hal/dbus are - hal-0.5.5.1-r3 (wich wants >=dbus-0.50) - dbus-0.60-r3 This could explain the "ping-pong"
Yes, I am using ivman (stable), as a matter of fact. So, I'm guessing the work around is to unmerge ivman, or use unstable?
I can't advice you since I don'use ivman :-( However there are guys on the french forum who use the last unstable ivman without problems. It would nevertheless only be a workaround : the fundamental problem remains ! Unmerging ivman could also be a solution but you will then lose automounting (unless you use something like kde-kioslaves or gnome-volume-manager or other older methods...)
(In reply to comment #3) > I can't advice you since I don'use ivman :-( > However there are guys on the french forum who use the last unstable ivman > without problems. > > It would nevertheless only be a workaround : the fundamental problem remains ! > > Unmerging ivman could also be a solution but you will then lose automounting > (unless you use something like kde-kioslaves or gnome-volume-manager or other > older methods...) > I get the same ping-pong but I am not using ivman. Here equery depends only shows kdebase-3.4.3-r1 depending on dbus and hal.
(In reply to comment #4) > I get the same ping-pong but I am not using ivman. Here equery depends only > shows kdebase-3.4.3-r1 depending on dbus and hal. > Replying to myself. I fixed the ping-pong by running revdep-rebuild which also indicated gnome-vfs as dependent on dbus/hal. Doing an emerge gnome-vfs resulted in an upgrade of gnome-vfs (that was not shown by emerge -upvD world) All is fine here and maybe it helps the original poster.
there is somoething in the hal emerge where it says something about running revdep-rebuild because the API/ABI changed. running revdep-rebuild gives me: [ebuild UD] sys-apps/dbus-0.23.4-r1 [0.60-r3] [ebuild UD] sys-apps/hal-0.4.8 [0.5.5.1-r3] [ebuild R ] sys-apps/ivman-0.5_pre2 which then downgrades hal/dbus again, and rebuilds ivman. emerge -NuD after the revdep-rebuild (without the -p) gives: [ebuild U ] sys-apps/dbus-0.60-r3 [0.23.4-r1] [ebuild U ] sys-apps/hal-0.5.5.1-r3 [0.4.8] next emerge gives me: [ebuild UD] sys-apps/dbus-0.23.4-r1 [0.60-r3] [ebuild UD] sys-apps/hal-0.4.8 [0.5.5.1-r3] so, we're back in the infinite loop. trying to revdep-rebuild twice is even messier, as it tries to upgrade hal/dbus, rebuild k3b, kioslaves, vlc, downgrade hal/dbus, rebuild ivman, and then eventually fails trying to build pmount. I'm getting to the point where I'm thinking about using ivman unstable.
genstef: You need to stablize a new version of ivman. Reassigning directly to you rather then Gentopia.
x86 team: please stabilize the latest version of ivman
*** This bug has been marked as a duplicate of 120582 ***
