| 1 |
On 11/1/05, John Myers <electronerd@×××××××××××××.net> wrote: |
| 2 |
> |
| 3 |
> On Tuesday 01 November 2005 02:19, Fernando Meira wrote: |
| 4 |
> > So, there are some missing libraries and others causing conflicts.. |
| 5 |
> don't |
| 6 |
> > know if that was caused by the power-down, or something while updating |
| 7 |
> was |
| 8 |
> > running, but how can I fix this? Should I reemerge some packages? If so, |
| 9 |
> > which ones? |
| 10 |
> try reemerging dbus and hal, in that order. |
| 11 |
|
| 12 |
|
| 13 |
Thanks for the quick reply! |
| 14 |
This is what emerge would do: |
| 15 |
|
| 16 |
# emerge -Dav dbus hal |
| 17 |
|
| 18 |
Calculating dependencies ...done! |
| 19 |
[ebuild R ] sys-apps/dbus-0.36.2 +X -debug -doc -gtk -mono +python +qt +xml2 |
| 20 |
0 kB |
| 21 |
[ebuild UD] sys-apps/dbus-0.23.4-r1 [0.36.2] +X -debug -gtk -mono +python |
| 22 |
+qt +xml2 0 kB |
| 23 |
[ebuild R ] sys-apps/hal-0.4.7-r2 -debug -doc -livecd -pcmcia 0 kB |
| 24 |
|
| 25 |
So, i updated dbus, but for hal, it would downgrade dbus... isn't it strange |
| 26 |
that it upgraded it and now wants to downgrade it.. with no emerge --sync in |
| 27 |
between? And, should I do this? |
Archives