1 |
On Friday 15 January 2010 00:36:16 hkml@×××××××××××.de wrote: |
2 |
> Dear group, |
3 |
> |
4 |
> I'm using gentoo for more than three years now and using the gentoo |
5 |
> packaging system in general is exactly what I expect from a packaging |
6 |
> system. You just open a shell somewhere on your virtual desktop, start a |
7 |
> process and the rest is done automatically (in general). |
8 |
> |
9 |
> But, when it comes to packages blocking each other I simply have to guess, |
10 |
> what to do next and sometimes I fail in guessing the right things I once |
11 |
> removed the wrong package, which left me with a system without working |
12 |
> packaging system - a very bad experience. In fact I could only solve this |
13 |
> problem by copying a dynamic library from another linux installation to |
14 |
> reanimate emerge. |
15 |
> |
16 |
> So some weeks ago I was too busy to take care of some conflicts caused by |
17 |
> the end of support for KDE 3.5). I stopped updating, because I didn't have |
18 |
> the time to switch to newer KDE version and wanted to do that later on. |
19 |
|
20 |
Everything above this line is fascinating but completely unrelated to your |
21 |
post. Please omit such in future |
22 |
|
23 |
> Now I want to upgrade, but I would like to better understand the messages |
24 |
> telling me the conflicting packets. A current call to 'emerge --update |
25 |
> --deep --ask world' gives me the following conflicts: |
26 |
> |
27 |
> |
28 |
> * Error: The above package list contains packages which cannot be |
29 |
> * installed at the same time on the same system. |
30 |
> |
31 |
> ('installed', '/', 'sys-fs/device-mapper-1.02.24-r1', 'nomerge') pulled |
32 |
> in by |
33 |
> |
34 |
> >=sys-fs/device-mapper-1.00.07-r1 required by ('installed', '/', |
35 |
> > 'sys-fs/cryptsetup-1.0.6-r2', 'nomerge') |
36 |
|
37 |
Read it backwards from the bottom up. It means that cryptsetup requires |
38 |
device-mapper (a version greater than 1.00.07-r1) and portage has chosen |
39 |
device-mapper-1.02.24-r1 |
40 |
|
41 |
> ('ebuild', '/', 'kde-base/kdebase-data-4.3.3', 'merge') pulled in by |
42 |
> |
43 |
> >=kde-base/kdebase-data-4.3.3[-kdeprefix] required by ('ebuild', '/', |
44 |
> > 'kde-base/kdelibs-4.3.3-r1', 'merge') |
45 |
> > =kde-base/kdebase-data-4.3.3[-kdeprefix] required by ('ebuild', '/', |
46 |
> > 'kde-base/kdebase-meta-4.3.3', 'merge') |
47 |
|
48 |
Same as above, except that both kdelibs and kdebase-meta have pulled in |
49 |
kdebase-data. Sometimes the list of package that pull in other gets very long |
50 |
and the list might be truncated with a message something like "plus 33 |
51 |
others..." |
52 |
|
53 |
> ('installed', '/', 'app-arch/lzma-utils-4.32.7', 'nomerge') pulled in by |
54 |
> app-arch/lzma-utils required by ('ebuild', '/', |
55 |
> 'dev-libs/mpfr-2.4.1_p5', 'merge') app-arch/lzma-utils required by |
56 |
> ('ebuild', '/', 'dev-texlive/texlive-basic-2008-r1', 'merge') |
57 |
> app-arch/lzma-utils required by ('ebuild', '/', |
58 |
> 'dev-texlive/texlive-latex-2008-r2', 'merge') (and 5 more) |
59 |
> |
60 |
> ('installed', '/', 'kde-base/akregator-3.5.10', 'nomerge') pulled in by |
61 |
> |
62 |
> >=kde-base/akregator-3.5.10:3.5 required by ('installed', '/', |
63 |
> > 'kde-base/konqueror-akregator-3.5.10', 'nomerge') |
64 |
> |
65 |
> ('ebuild', '/', 'sys-fs/udev-146-r1', 'merge') pulled in by |
66 |
> virtual/dev-manager required by world |
67 |
> |
68 |
> >=sys-fs/udev-103 required by ('ebuild', '/', 'media-gfx/iscan-2.21.0', |
69 |
> > 'merge') =sys-fs/udev-124 required by ('installed', '/', |
70 |
> > 'sys-fs/cryptsetup-1.0.6-r2', 'nomerge') |
71 |
> |
72 |
> (and 3 more) |
73 |
> |
74 |
> ('ebuild', '/', 'net-wireless/bluez-4.39-r2', 'merge') pulled in by |
75 |
> net-wireless/bluez required by ('ebuild', '/', 'gnome-base/gvfs-1.2.3', |
76 |
> 'merge') net-wireless/bluez required by ('ebuild', '/', |
77 |
> 'kde-base/solid-4.3.3', 'merge') |
78 |
> |
79 |
> ('ebuild', '/', 'kde-base/akregator-4.3.3', 'merge') pulled in by |
80 |
> |
81 |
> >=kde-base/akregator-4.3.3[-kdeprefix] required by ('ebuild', '/', |
82 |
> > 'kde-base/kdepim-meta-4.3.3', 'merge') |
83 |
> |
84 |
> ('ebuild', '/', 'app-arch/xz-utils-4.999.9_beta', 'merge') pulled in by |
85 |
> app-arch/xz-utils required by ('ebuild', '/', |
86 |
> 'app-arch/libarchive-2.7.1-r1', 'merge') |
87 |
> |
88 |
> ('installed', '/', 'net-wireless/bluez-libs-3.36', 'nomerge') pulled in |
89 |
> by net-wireless/bluez-libs required by ('installed', '/', |
90 |
> 'net-libs/libpcap-1.0.0-r2', 'nomerge') |
91 |
> |
92 |
> ('installed', '/', 'kde-base/kdebase-data-3.5.10', 'nomerge') pulled in |
93 |
> by |
94 |
> |
95 |
> >=kde-base/kdebase-data-3.5.10:3.5 required by ('installed', '/', |
96 |
> > 'kde-base/kcontrol-3.5.10', 'nomerge') |
97 |
> > =kde-base/kdebase-data-3.5.10:3.5 required by ('installed', '/', |
98 |
> > 'kde-base/kicker-3.5.10-r1', 'nomerge') |
99 |
> |
100 |
> For me some of the messages are mysterious. What is e.g. the exact meaning |
101 |
> of the four components in |
102 |
> ('ebuild', '/', 'net-wireless/bluez-4.39-r2', 'merge') or |
103 |
> ('installed', '/', 'kde-base/akregator-3.5.10', 'nomerge') |
104 |
|
105 |
It's just a statement that something will be merged, followed by the packages |
106 |
that caused it to be merged. It's all usually of the form |
107 |
|
108 |
"exact package" pulled in by |
109 |
"package spec from an ebuild" |
110 |
pulled in by |
111 |
"something else" |
112 |
|
113 |
Apparently you have konqueror-akregator in world (nothing else is pulling it |
114 |
in) which causes akregator to be merged. You must remove konqueror-akregator |
115 |
manually using |
116 |
|
117 |
emerge -C konqueror-akregator |
118 |
|
119 |
> How should I resolve the conflict |
120 |
> net-libs/libpcap-1.0.0-r2 versus gnome-base/gvfs-1.2.3 and |
121 |
> kde-base/solid-4.3.3 I don't even have any bluetooth device in my |
122 |
> computer. Should I fiddle with the USE flags of KDE and Gnome or libpcap |
123 |
> to avoid they pull in net-wireless/bluez? |
124 |
|
125 |
You don't have a conflict per the above. |
126 |
|
127 |
Actually, you removed the relevant part of the output and didn't post it, so |
128 |
now we can't help you. |
129 |
|
130 |
Please repost the full output. |
131 |
|
132 |
When you identify the blocker, you have to ask yourself some intelligent |
133 |
questions, like: |
134 |
|
135 |
portage wants to merge packages A and B, but the ebuilds say that A and B |
136 |
cannot be installed together. What is pulling in A and what is pulling in B, |
137 |
and why? It might be a hard dependency, it might be a USE flag issue, it might |
138 |
be that the package is in world. Also learn how to read ebuilds |
139 |
|
140 |
> Which packets are causing the device-mapper conflict? |
141 |
|
142 |
Not the foggiest idea - you removed the info that tells me that :-) |
143 |
|
144 |
> What is the most secure way to switch to KDE 4? Should I remove the |
145 |
> packages konqueror-akregator, kcontrol and kicker, then update to KDE 4 |
146 |
> and then reinstall those packets? |
147 |
|
148 |
First get rid of KDE-3.5 completely, then install KDE-4: |
149 |
|
150 |
Inspect you world file and unmerge everything related the KDE-3.5. Then run a |
151 |
--depclean o remove dependencies not in world, then run emerge -uND world and |
152 |
double check that nothing kde-3.5 related is pulled in. Rinse and repeat till |
153 |
this is true. |
154 |
|
155 |
Then merge KDE-4 as usual |
156 |
|
157 |
> Maybe someone can explain how to proceed best. Are there some things I can |
158 |
> check using equery or whatsoever to support my decisions? I'm feeling |
159 |
> unsure how to handle these problems keeping the risk to leave my system |
160 |
> (partially) unusable as small as possible. Maybe someone can give me a |
161 |
> hint, where to find more information about how to handle conflicts in the |
162 |
> packaging system. |
163 |
|
164 |
Before anyone explains to you how to drive gentoo, you should help yourself |
165 |
first: |
166 |
|
167 |
1. Re-read the install document. All of it. Maybe read it three times. |
168 |
|
169 |
2. Read the man pages, all of them, several times. You can find this list |
170 |
with"equery files portage" and looking for files under "/usr/share/man" |
171 |
|
172 |
|
173 |
There is no easy way through this, you have to understand how portage and it's |
174 |
builds work and that involves study on your part. |
175 |
|
176 |
-- |
177 |
alan dot mckinnon at gmail dot com |