| View previous topic :: View next topic |
| Author |
Message |
cfgauss
l33t
Joined: 18 May 2005
Posts: 688
Location: USA
|
 Posted: Sun Dec 01, 2013 12:00 am Post subject: [SOLVED] Emerge problems with libiconv, systemd, udev |
 |
|
The latest emerge world was a mess. Here are some errors:
| Code: | !!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
virtual/libiconv:0
(virtual/libiconv-0::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(virtual/libiconv-0::gentoo, ebuild scheduled for merge) pulled in by
virtual/libiconv[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?] required by (dev-libs/glib-2.36.4-r1::gentoo, ebuild scheduled for merge)
...
(sys-apps/systemd-208-r2::gentoo, ebuild scheduled for merge) pulled in by
sys-apps/systemd required by (gnome-base/gnome-settings-daemon-3.8.6.1::gentoo, ebuild scheduled for merge)
>=sys-apps/systemd-207 required by (sys-apps/gentoo-systemd-integration-2::gentoo, ebuild scheduled for merge)
>=sys-apps/systemd-44-r1[pam] required by (sys-auth/pambase-20120417-r3::gentoo, ebuild scheduled for merge)
(sys-fs/udev-208::gentoo, ebuild scheduled for merge) pulled in by
>=sys-fs/udev-208[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,gudev?,introspection?,kmod?,selinux?,static-libs?] (>=sys-fs/udev-208[abi_x86_64(-),gudev,introspection,kmod]) required by (virtual/udev-208::gentoo, ebuild scheduled for merge)
sys-fs/udev required by @selected
|
My system is KDE. I don't know why there's so much dependency on Gnome.
Any pointers would be gratefully received.
[SOLVED] I emerged with the -tree flag to see where systemd was being pulled in. Hu (below) was right that it's a USE flag for Gnome packages so I removed these packages. Inexplicably I had added systemd as a USE flag for pambase. (Why, I wonder?) Taking that out expunged the last trace of systemd. I then also switched to the KDE-specific desktop profile as well. This might help portage avoid Gnome dependencies.
I'm guessing that I don't ever need to install systemd. Hu, many thanks for the suggestion. [/SOLVED]
Last edited by cfgauss on Sun Dec 01, 2013 3:37 am; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21633
|
| Posted: Sun Dec 01, 2013 12:09 am Post subject: |
|
|
| If you run a pure KDE system, you may find it useful to mask GNOME related packages so that Portage cannot use them to satisfy dependencies. In some cases, that seems to generate more helpful error messages. |
|
| Back to top |
|
|
cfgauss
l33t
Joined: 18 May 2005
Posts: 688
Location: USA
|
| Posted: Sun Dec 01, 2013 12:33 am Post subject: |
|
|
| Hu wrote: | | If you run a pure KDE system, you may find it useful to mask GNOME related packages so that Portage cannot use them to satisfy dependencies. In some cases, that seems to generate more helpful error messages. |
I masked a few Gnome packages but am still left with libiconv, systemd, and udev blocks (listed above) and these:
| Code: | [blocks B ] sys-apps/systemd ("sys-apps/systemd" is blocking sys-fs/udev-204, sys-fs/udev-208)
[blocks B ] sys-fs/udev ("sys-fs/udev" is blocking sys-apps/systemd-208-r2) |
Any pointers on how to unblock would be gratefully appreciated. |
|
| Back to top |
|
|
cfgauss
l33t
Joined: 18 May 2005
Posts: 688
Location: USA
|
| Posted: Sun Dec 01, 2013 2:43 am Post subject: |
|
|
Here a Gentoo Wiki describing how to install sys-apps/systemd, which seems to block sys-fs/udev. It states that systemd is an "alternate init system."
What's the current init system called?
Can I keep the current one and not install systemd?
Thanks for helping me understand what systemd is and if I need/want it. |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21633
|
| Posted: Sun Dec 01, 2013 4:48 pm Post subject: |
|
|
It is an alternative to OpenRC. OpenRC can use udev, but systemd wants to own your devices as well as your init system. If you wanted to run GNOME 3.8, you would be required to install systemd. Otherwise, I would suggest avoiding systemd for now. You can use it, but you may spend quite a bit of time getting it working. I suggest temporarily masking systemd so that Portage will help you trace why it is requested.
Update: it seems you solved it already. Good to see that it works for you now. You probably enabled systemd in response to a Portage diagnostic asking for it, before you realized how invasive systemd tends to be. |
|
| Back to top |
|
|
cfgauss
l33t
Joined: 18 May 2005
Posts: 688
Location: USA
|
| Posted: Sun Dec 01, 2013 8:38 pm Post subject: |
|
|
| Hu wrote: | It is an alternative to OpenRC. OpenRC can use udev, but systemd wants to own your devices as well as your init system. If you wanted to run GNOME 3.8, you would be required to install systemd. Otherwise, I would suggest avoiding systemd for now. You can use it, but you may spend quite a bit of time getting it working. I suggest temporarily masking systemd so that Portage will help you trace why it is requested.
Update: it seems you solved it already. Good to see that it works for you now. You probably enabled systemd in response to a Portage diagnostic asking for it, before you realized how invasive systemd tends to be. |
Many thanks for this explanation. I did mask systemd and, as a KDE user, I hope I can stave this off for a while. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
