Fernando Meira schreef: > This is what emerge would do: > > # emerge -Dav dbus hal > > Calculating dependencies ...done! [ebuild R ] sys-apps/dbus-0.36.2 +X > -debug -doc -gtk -mono +python +qt +xml2 0 kB [ebuild UD] > sys-apps/dbus-0.23.4-r1 [0.36.2] +X -debug -gtk -mono +python +qt > +xml2 0 kB [ebuild R ] sys-apps/hal-0.4.7-r2 -debug -doc -livecd > -pcmcia 0 kB > > So, i updated dbus, but for hal, it would downgrade dbus... isn't it > strange that it upgraded it and now wants to downgrade it.. with no > emerge --sync in between? And, should I do this? > No, it's not weird, just kinda a pain.
HAL and dbus are tied together, and dbus is tied to k3b. This happened to me, kinda, which is how I noticed it. What's happening is that the version of hal you have installed requires the version of dbus you have installed, but the version of K3b you currently have installed requires a lower version of dbus than the one you have (so it's downgrading dbus). Had you been able to install k3b, then it would have all worked out (the upgrade to k3b can use the upgraded dbus). IIrc, the version of dbus you're downgrading to would break HAL (because it's a lower version than the one required by the higher version of HAL-- they're very tightly tied together). ATM, you have the "correct" versions of hal and dbus installed. What I would do (and what I think I may have in fact done) was: 1) unmerge k3b totally. Don't worry, it's not for long. 2) reboot to re-initialize hal and dbus with the new versions (you might be able to do this with stopping and restarting the services, but I found it generally more reliable to just reboot, so I did). 3) re-emerge k3b (which should get you the new version which should detect that the required verisons of HAL and dbus are in use). If this fails for some reason, try re-emerging HAL and dbus again; they may have installed with faults due to the power outage, then try steps 2 and 3 again. Or you could just remove the "hal" USE flag from k3b, so it doesn't use HAL and dbus at all, but I don't know the effects of that (it is, however, optional, so the effects shouldn't be that severe). I didn't want to do that, though, when I ran into this problem (or one very similar). Hope this helps, Holly -- gentoo-user@gentoo.org mailing list
