1 |
Apparently, though unproven, at 04:58 on Friday 17 September 2010, Dale did |
2 |
opine thusly: |
3 |
|
4 |
> Hi folks, |
5 |
> |
6 |
> The latest KDE 4.5.1 has hit the tree. It made it there a few days |
7 |
> ago. Yeppie!! It is masked but I wanted to try to install it again. |
8 |
> The last time was a mess to say it lightly. I use autounmask to unmask |
9 |
> it. I use this command: |
10 |
> |
11 |
> autounmask kde-base/kde-meta-4.5.1 |
12 |
> |
13 |
> I don't use the -n option but it doesn't seem to matter even if I do. |
14 |
> I'm on portage-2.2_rc67 and autounmask-0.27 which is the only version I |
15 |
> see in the tree. After I run autounmask and then do a emerge -uvDNa |
16 |
> world, I get this: |
17 |
> |
18 |
> root@smoker / # emerge -uvDNa world |
19 |
> |
20 |
> These are the packages that would be merged, in order: |
21 |
> |
22 |
> Calculating dependencies... done! |
23 |
> |
24 |
> emerge: there are no ebuilds to satisfy |
25 |
> ">=kde-base/kdelibs-9999[-kdeprefix,-aqua]". |
26 |
> (dependency required by "kde-base/liboxygenstyle-9999" [installed]) |
27 |
> (dependency required by "kde-base/kdebase-meta-4.5.1" [ebuild]) |
28 |
> (dependency required by "kde-base/kde-meta-4.5.1" [ebuild]) |
29 |
> (dependency required by "@world" [argument]) |
30 |
> |
31 |
> root@smoker / # |
32 |
> |
33 |
> If I add that kdelibs package to the unmask file, it just goes to the |
34 |
> nest blocker and this continues until I get the idea something is not |
35 |
> working right. So, is autounmask not working right? Am I not doing |
36 |
> something right? Am I missing something? |
37 |
|
38 |
|
39 |
It's not kdelibs that's your problem, it is liboxygen style. portage wants to |
40 |
use version 9999 from svn and it's that that is pulling in kdelibs. |
41 |
|
42 |
Fix your unmask for liboxygenstyle, then see with -t why it wants the -9999 |
43 |
version |
44 |
|
45 |
|
46 |
-- |
47 |
alan dot mckinnon at gmail dot com |