1 |
Hi Alan, |
2 |
|
3 |
first of all, which portage version are you using? Even if you are otherwise |
4 |
always running a stable system, in this case it might be useful to update |
5 |
portage (only) to ~arch. The errors that you are seeing are in an area of the |
6 |
dependency resolver that people are actively working on now, and nearly all |
7 |
gentoo devs are running ~arch portage. |
8 |
|
9 |
Add |
10 |
sys-apps/portage ~amd64 |
11 |
in /etc/portage/package.accept_keywords, then |
12 |
emerge -a1u portage |
13 |
|
14 |
Then, let's first fix the REQUIRED_USE issue from the end of the log. This is |
15 |
something portage cannot do on its own. |
16 |
|
17 |
> !!! The ebuild selected to satisfy ">=dev-libs/libattica-0.4.2" has |
18 |
> unmet requirements. - dev-libs/libattica-0.4.2::gentoo USE="-debug -qt4 |
19 |
> (-qt5) -test" |
20 |
> |
21 |
> The following REQUIRED_USE flag constraints are unsatisfied: |
22 |
> exactly-one-of ( qt4 qt5 ) |
23 |
> |
24 |
> (dependency required by "kde-base/kdelibs-4.12.5" [ebuild]) |
25 |
> (dependency required by "@selected" [set]) |
26 |
> (dependency required by "@world" [argument]) |
27 |
|
28 |
I suggest you set the qt4 use flag for libattica (since qt5 is not in the tree |
29 |
yet), e.g. add |
30 |
dev-libs/libattica qt4 |
31 |
to /etc/portage/package.use |
32 |
|
33 |
Then try again... Things might work now. |
34 |
If not, try backtrack 1000. |
35 |
If not, ... better send the new error message. |
36 |
|
37 |
Alternatively, |
38 |
|
39 |
> app-text/poppler:0 |
40 |
> |
41 |
> (app-text/poppler-0.24.3::gentoo, installed) pulled in by |
42 |
> app-text/poppler:0/43=[cxx,jpeg,lcms,tiff,xpdf-headers(+)] required |
43 |
> by (net-print/cups-filters-1.0.53::gentoo, installed) |
44 |
> |
45 |
> (app-text/poppler-0.26.1::gentoo, ebuild scheduled for merge) pulled |
46 |
> in by (no parents that aren't satisfied by other packages in this slot) |
47 |
|
48 |
All the other messages are caused by the subslot rebuild mechanism: If you |
49 |
check in detail, from the "two different packages" pulled in, the old one |
50 |
always has a "subslot setting", e.g. app-text/poppler:0/43 (the "/43") and the |
51 |
new required version has a different subslot (not printed unfortunately, but |
52 |
app-text/poppler-0.26.1 has "/46"). Similar reasoning applies to ICU, Perl, |
53 |
and libpng. |
54 |
|
55 |
This is the area actively under improvement that I mentioned above. Basically |
56 |
the difference between "/44" and "/46" tells portage "After upgrading poppler, |
57 |
rebuild everything that links against it". |
58 |
|
59 |
While the automated rebuilds are a very nice thing (they make revdep-rebuild |
60 |
and perl-cleaner obsolete), they also make figuring things out for portage |
61 |
very very difficult. So, one last resort is to switch them off. Not |
62 |
recommended for regular operation, just if there is absolutely no way to get |
63 |
around problems. |
64 |
|
65 |
emerge -vtpuND --backtrack=100 --color y --ignore-built-slot-operator-deps y |
66 |
world |
67 |
|
68 |
What happens now? |
69 |
|
70 |
(If you run this command without the -p you will have to run "emerge |
71 |
@preserved-rebuild" and "perl-cleaner --all" immediately afterwards, maybe |
72 |
more than once. Just like in old times.) |
73 |
|
74 |
Cheers from Regensburg, |
75 |
Andreas |
76 |
|
77 |
-- |
78 |
|
79 |
Andreas K. Huettel |
80 |
Gentoo Linux developer |
81 |
dilfridge@g.o |
82 |
http://www.akhuettel.de/ |