1 |
The dependency graph that seems to be murdering me right now seems to be: |
2 |
|
3 |
|
4 |
kde -> wayland -> gles2 -> egl -> |
5 |
|
6 |
|
7 |
##################### |
8 |
.............................. |
9 |
|
10 |
[ebuild N ] kde-plasma/plasma-meta-5.5.5:5::gentoo |
11 |
USE="display-manager gtk pam pulseaudio sddm sdk wallpapers -bluetooth |
12 |
-mediacenter -networkmanager" 0 KiB |
13 |
[ebuild NS ] kde-apps/kde-meta-15.08.3:5::gentoo |
14 |
[4.14.3-r1:4::gentoo] 0 KiB |
15 |
[uninstall ] kde-apps/kde-meta-4.14.3-r1:4::gentoo USE="nls sdk |
16 |
-accessibility (-aqua) -kdepim -minimal" |
17 |
[blocks b ] kde-apps/kde-meta:4 ("kde-apps/kde-meta:4" is blocking |
18 |
kde-apps/kde-meta-15.08.3) |
19 |
[ebuild U ] dev-lang/mono-4.2.2.30::gentoo [4.2.2.10-r1::gentoo] |
20 |
USE="nls (-doc) -minimal -pax_kernel -xen" 0 KiB |
21 |
[ebuild N ] dev-dotnet/nuget-2.8.3::gentoo 0 KiB |
22 |
[ebuild U ] dev-dotnet/libgdiplus-4.2-r2::gentoo [4.2-r1::gentoo] |
23 |
USE="cairo" 0 KiB |
24 |
[ebuild U ] dev-util/monodevelop-5.9.5.9-r1::gentoo |
25 |
[3.0.2-r1::gentoo] USE="git gnome%* subversion -qtcurve%" 0 KiB |
26 |
|
27 |
Total: 119 packages (21 upgrades, 32 new, 54 in new slots, 12 |
28 |
reinstalls, 80 uninstalls), Size of downloads: 395,848 KiB |
29 |
Conflict: 80 blocks |
30 |
|
31 |
WARNING: One or more updates/rebuilds have been skipped due to a |
32 |
dependency conflict: |
33 |
|
34 |
dev-qt/qtgui:5 |
35 |
|
36 |
(dev-qt/qtgui-5.5.1-r1:5/5::gentoo, ebuild scheduled for merge) |
37 |
conflicts with |
38 |
~dev-qt/qtgui-5.5.1[-egl] required by |
39 |
(dev-qt/qtmultimedia-5.5.1-r2:5/5::gentoo, installed) |
40 |
^^^^ |
41 |
|
42 |
tortoise ~ # |
43 |
##################### |
44 |
|
45 |
|
46 |
|
47 |
Dale wrote: |
48 |
> Neil Bothwick wrote: |
49 |
>> |
50 |
>> Why ask the same question again when you got an answer last time? |
51 |
>> |
52 |
>> Hint: look at the output for asciidoc. |
53 |
>> -- |
54 |
>> Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
55 |
> I have to add this. From what I understand about the scripts he is |
56 |
> using, he is blindly letting emerge do updates without checking to see |
57 |
> if the updates fall into line with what he *needs*. If I read it |
58 |
> correctly, any USE flag change will be missed until it hits the fan and |
59 |
> is broken. That would then mean taking a lot of time to go back through |
60 |
> logs and figuring out just when it went wrong and most importantly, what |
61 |
> caused it and how to fix it. Since the change could have happened |
62 |
> several updates ago, that could involve some work and a lot of rebuilding. |
63 |
> |
64 |
> Doing the sync in a script and even getting a email or something with |
65 |
> the -p output is fine but updating blindly is not a good idea. |
66 |
> |
67 |
> At this point, I think I understand why he is having so much trouble. |
68 |
> At the very least, check to see what USE flags are changing before doing |
69 |
> updates. There are other things that are important but that is one that |
70 |
> changes a good bit. |
71 |
> |
72 |
> Dale |
73 |
> |
74 |
> :-) :-) |
75 |
> |
76 |
> |
77 |
|
78 |
|
79 |
-- |
80 |
IQ is a measure of how stupid you feel. |
81 |
|
82 |
Powers are not rights. |