1 |
Dear group, |
2 |
|
3 |
I'm using gentoo for more than three years now and using the gentoo packaging system |
4 |
in general is exactly what I expect from a packaging system. You just open a shell |
5 |
somewhere on your virtual desktop, start a process and the rest is done automatically |
6 |
(in general). |
7 |
|
8 |
But, when it comes to packages blocking each other I simply have to guess, what to do next |
9 |
and sometimes I fail in guessing the right things I once removed the wrong package, |
10 |
which left me with a system without working packaging system - a very bad experience. In fact |
11 |
I could only solve this problem by copying a dynamic library from another linux installation |
12 |
to reanimate emerge. |
13 |
|
14 |
So some weeks ago I was too busy to take care of some conflicts caused by the end of support |
15 |
for KDE 3.5). I stopped updating, because I didn't have the time to switch to newer KDE |
16 |
version and wanted to do that later on. |
17 |
|
18 |
Now I want to upgrade, but I would like to better understand the messages telling me the |
19 |
conflicting packets. A current call to 'emerge --update --deep --ask world' gives me the |
20 |
following conflicts: |
21 |
|
22 |
|
23 |
* Error: The above package list contains packages which cannot be |
24 |
* installed at the same time on the same system. |
25 |
|
26 |
('installed', '/', 'sys-fs/device-mapper-1.02.24-r1', 'nomerge') pulled in by |
27 |
>=sys-fs/device-mapper-1.00.07-r1 required by ('installed', '/', 'sys-fs/cryptsetup-1.0.6-r2', 'nomerge') |
28 |
|
29 |
('ebuild', '/', 'kde-base/kdebase-data-4.3.3', 'merge') pulled in by |
30 |
>=kde-base/kdebase-data-4.3.3[-kdeprefix] required by ('ebuild', '/', 'kde-base/kdelibs-4.3.3-r1', 'merge') |
31 |
>=kde-base/kdebase-data-4.3.3[-kdeprefix] required by ('ebuild', '/', 'kde-base/kdebase-meta-4.3.3', 'merge') |
32 |
|
33 |
('installed', '/', 'app-arch/lzma-utils-4.32.7', 'nomerge') pulled in by |
34 |
app-arch/lzma-utils required by ('ebuild', '/', 'dev-libs/mpfr-2.4.1_p5', 'merge') |
35 |
app-arch/lzma-utils required by ('ebuild', '/', 'dev-texlive/texlive-basic-2008-r1', 'merge') |
36 |
app-arch/lzma-utils required by ('ebuild', '/', 'dev-texlive/texlive-latex-2008-r2', 'merge') |
37 |
(and 5 more) |
38 |
|
39 |
('installed', '/', 'kde-base/akregator-3.5.10', 'nomerge') pulled in by |
40 |
>=kde-base/akregator-3.5.10:3.5 required by ('installed', '/', 'kde-base/konqueror-akregator-3.5.10', 'nomerge') |
41 |
|
42 |
('ebuild', '/', 'sys-fs/udev-146-r1', 'merge') pulled in by |
43 |
virtual/dev-manager required by world |
44 |
>=sys-fs/udev-103 required by ('ebuild', '/', 'media-gfx/iscan-2.21.0', 'merge') |
45 |
>=sys-fs/udev-124 required by ('installed', '/', 'sys-fs/cryptsetup-1.0.6-r2', 'nomerge') |
46 |
(and 3 more) |
47 |
|
48 |
('ebuild', '/', 'net-wireless/bluez-4.39-r2', 'merge') pulled in by |
49 |
net-wireless/bluez required by ('ebuild', '/', 'gnome-base/gvfs-1.2.3', 'merge') |
50 |
net-wireless/bluez required by ('ebuild', '/', 'kde-base/solid-4.3.3', 'merge') |
51 |
|
52 |
('ebuild', '/', 'kde-base/akregator-4.3.3', 'merge') pulled in by |
53 |
>=kde-base/akregator-4.3.3[-kdeprefix] required by ('ebuild', '/', 'kde-base/kdepim-meta-4.3.3', 'merge') |
54 |
|
55 |
('ebuild', '/', 'app-arch/xz-utils-4.999.9_beta', 'merge') pulled in by |
56 |
app-arch/xz-utils required by ('ebuild', '/', 'app-arch/libarchive-2.7.1-r1', 'merge') |
57 |
|
58 |
('installed', '/', 'net-wireless/bluez-libs-3.36', 'nomerge') pulled in by |
59 |
net-wireless/bluez-libs required by ('installed', '/', 'net-libs/libpcap-1.0.0-r2', 'nomerge') |
60 |
|
61 |
('installed', '/', 'kde-base/kdebase-data-3.5.10', 'nomerge') pulled in by |
62 |
>=kde-base/kdebase-data-3.5.10:3.5 required by ('installed', '/', 'kde-base/kcontrol-3.5.10', 'nomerge') |
63 |
>=kde-base/kdebase-data-3.5.10:3.5 required by ('installed', '/', 'kde-base/kicker-3.5.10-r1', 'nomerge') |
64 |
|
65 |
|
66 |
For me some of the messages are mysterious. What is e.g. the exact meaning of |
67 |
the four components in |
68 |
('ebuild', '/', 'net-wireless/bluez-4.39-r2', 'merge') or |
69 |
('installed', '/', 'kde-base/akregator-3.5.10', 'nomerge') |
70 |
|
71 |
How should I resolve the conflict |
72 |
net-libs/libpcap-1.0.0-r2 versus gnome-base/gvfs-1.2.3 and kde-base/solid-4.3.3 |
73 |
I don't even have any bluetooth device in my computer. Should I fiddle with the USE flags of |
74 |
KDE and Gnome or libpcap to avoid they pull in net-wireless/bluez? |
75 |
|
76 |
Which packets are causing the device-mapper conflict? |
77 |
|
78 |
What is the most secure way to switch to KDE 4? Should I remove the packages konqueror-akregator, |
79 |
kcontrol and kicker, then update to KDE 4 and then reinstall those packets? |
80 |
|
81 |
Maybe someone can explain how to proceed best. Are there some things I can check using |
82 |
equery or whatsoever to support my decisions? I'm feeling unsure how to handle these |
83 |
problems keeping the risk to leave my system (partially) unusable as small as possible. |
84 |
Maybe someone can give me a hint, where to find more information about how to handle conflicts |
85 |
in the packaging system. |
86 |
|
87 |
Sorry for the long mail. |
88 |
|
89 |
Cheers, Heinz |