1 |
On Thu, 22 May 2014 19:40:51 +1000, Zoltán Kócsi wrote: |
2 |
|
3 |
> > the output you posted is hard to read because your mailer wrapped it |
4 |
> > but it may be that updating sysvinit manually first will clear it. |
5 |
> > |
6 |
> > emerge -1a sysvinit |
7 |
> |
8 |
> It did it indeed, so the immediate problem is solved, thanks a lot for |
9 |
> that. |
10 |
> |
11 |
> However, I'd be obliged if you could tell me what was wrong and why an |
12 |
> update cleared it? I genuinely don't understand what goes on and I'd be |
13 |
> keen to learn about how Gentoo manages dependencies. |
14 |
|
15 |
To be honest, it was a bit of a guess, because I had so much trouble |
16 |
parsing the wrapped emerge output. The basic problem is that you have a |
17 |
package that portage wants to update, but another package wants to keep |
18 |
it at the same version. This is generally solved by either updating |
19 |
individual packages manually or unmerging the package causing the |
20 |
problem and then letting portage pull in the correct versions. |
21 |
|
22 |
In most cases, portage can now handle these things automatically but |
23 |
there are time it cannot. This may well have been caused by the various |
24 |
USE flag changes in your situation. If you make massive changes to your |
25 |
USE flags after installing from a stage 3, you can often see this sort of |
26 |
behaviour. The solution is generally to take small steps, change a few |
27 |
flags at a time. |
28 |
|
29 |
|
30 |
-- |
31 |
Neil Bothwick |
32 |
|
33 |
Always be sincere... whether you mean it or not! |