On 11/1/05, Neil Bothwick <[EMAIL PROTECTED]> wrote:
On Tue, 1 Nov 2005 11:36:52 +0100, Fernando Meira wrote:

> # 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?

The API changed between HAL 0.4.x and 0.5.x, you must have matching
versions of HAL and D-BUS

dbus-0.2* and hal-0.4.*
or
dbus-0.3* and hal-0.5.*

Ok... now I see what went wrong!
I have dbus in my package.keywords, so that's why it was updated to the new version 0.3*, while hal is not there and remained on the stable version 0.4*.. I have just masked the >dbus-0.3 and the problem should be fixed.. let's see how the remaining compilations go.. :)

Thanks!


Reply via email to