1 |
At Tue, 13 Oct 2009 15:02:25 +0200 Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
|
3 |
> qt*-4.5.1 blocks qt*-4.5.2. It's not a simple single package that you upgrade, |
4 |
> it's multiple packages and throughout the build you will have incompatible |
5 |
> packages installed at the same time. |
6 |
> |
7 |
> Either: |
8 |
> |
9 |
> unmerge all of qt |
10 |
> emerge all of qt |
11 |
> |
12 |
> or: |
13 |
> |
14 |
> upgrade to masked portage-2.2 which can deal with such things easily. |
15 |
> |
16 |
> Note that you will likely need to rebuild kdelibs and other stuff after |
17 |
> building qt. There's an elog about it. |
18 |
|
19 |
I do not have kde installed (I use gnome). I just did an |
20 |
eix --installed kde |
21 |
to confirm. |
22 |
|
23 |
I have 10 "qt" packages (confirmed with eix --installed qt) |
24 |
Seven begin with qt- and are at 4.5.1 with 4.5.2 available. |
25 |
The other three are qt PyQt PyQt4. |
26 |
None of the seven are in world. |
27 |
Have I understood correctly the procedure to be |
28 |
|
29 |
1. Unmerge these 7 (*not* 10) |
30 |
2. emerge --update --ask --newuse --deep --tree -v --with-bdeps=y world |
31 |
3. depclean and revdep-rebuild |
32 |
|
33 |
thanks to alan dale and peter for their help. |
34 |
|
35 |
allan |