1 |
On 11/1/05, Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> |
3 |
> On Tue, 1 Nov 2005 11:36:52 +0100, Fernando Meira wrote: |
4 |
> |
5 |
> > # emerge -Dav dbus hal |
6 |
> > |
7 |
> > Calculating dependencies ...done! |
8 |
> > [ebuild R ] sys-apps/dbus-0.36.2 +X -debug -doc -gtk -mono +python +qt |
9 |
> > +xml2 0 kB |
10 |
> > [ebuild UD] sys-apps/dbus-0.23.4-r1 [0.36.2] +X -debug -gtk -mono |
11 |
> > +python +qt +xml2 0 kB |
12 |
> > [ebuild R ] sys-apps/hal-0.4.7-r2 -debug -doc -livecd -pcmcia 0 kB |
13 |
> > |
14 |
> > So, i updated dbus, but for hal, it would downgrade dbus... isn't it |
15 |
> > strange that it upgraded it and now wants to downgrade it.. with no |
16 |
> > emerge --sync in between? And, should I do this? |
17 |
> |
18 |
> The API changed between HAL 0.4.x and 0.5.x, you must have matching |
19 |
> versions of HAL and D-BUS |
20 |
> |
21 |
> dbus-0.2* and hal-0.4.* |
22 |
> or |
23 |
> dbus-0.3* and hal-0.5.* |
24 |
|
25 |
|
26 |
Ok... now I see what went wrong! |
27 |
I have dbus in my package.keywords, so that's why it was updated to the new |
28 |
version 0.3*, while hal is not there and remained on the stable version |
29 |
0.4*.. I have just masked the >dbus-0.3 and the problem should be fixed.. |
30 |
let's see how the remaining compilations go.. :) |
31 |
|
32 |
Thanks! |