I have run into several problems with what should be the most basic of install processes, and I need to understand the gentoo approach so I can work with it. I don't just want work-arounds - I want to know how my thinking is wrong such that i am getting these results.
Following first the Gentoo amd64 install manual, and then the The X Server Configuration HOWTO, I have a working Gentoo system on my Lenovo T61.
Next, I am following the The Xfce Configuration Guide, and I run this command:
Code: Select all
merom ~ # emerge -Dvp xfce4-metaCode: Select all
The following keyword changes are necessary to proceed:
(see "package.accept_keywords" in the portage(5) man page for more details)
# required by dev-libs/dbus-glib-0.100.2
# required by xfce-base/xfce4-panel-4.10.0
# required by xfce-base/thunar-1.4.0[xfce_plugins_trash]
# required by xfce-base/xfdesktop-4.10.0[thunar]
# required by xfce-base/xfce4-meta-4.10
# required by xfce4-meta (argument)
=dev-libs/glib-2.34.3 ~amd64
# required by xfce-base/thunar-1.4.0[udev]
# required by xfce-base/xfdesktop-4.10.0[thunar]
# required by xfce-base/xfce4-meta-4.10
# required by xfce4-meta (argument)
=gnome-base/gvfs-1.14.2 ~amd64I also receive this, from the same command:
Code: Select all
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
sys-auth/pambase:0
(sys-auth/pambase-20101024-r2::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(sys-auth/pambase-20101024-r2::gentoo, ebuild scheduled for merge) pulled in by
sys-auth/pambase[consolekit] required by (sys-auth/polkit-0.110::gentoo, ebuild scheduled for merge)
virtual/udev:0
(virtual/udev-197-r2::gentoo, ebuild scheduled for merge) pulled in by
>=virtual/udev-197[gudev,hwdb] required by (sys-fs/udisks-2.1.0::gentoo, ebuild scheduled for merge)
virtual/udev[gudev] required by (xfce-base/thunar-1.4.0::gentoo, ebuild scheduled for merge)
virtual/udev[gudev] required by (gnome-base/gvfs-1.14.2::gentoo, ebuild scheduled for merge)
virtual/udev:=[gudev] required by (gnome-base/gvfs-1.12.3-r1::gentoo, ebuild scheduled for merge)
>=virtual/udev-197[gudev] required by (sys-power/upower-0.9.20-r2::gentoo, ebuild scheduled for merge)
(virtual/udev-197-r2::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)
sys-fs/udev:0
(sys-fs/udev-200::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(sys-fs/udev-200::gentoo, ebuild scheduled for merge) pulled in by
>=sys-fs/udev-197-r8[gudev?,hwdb?,introspection?,keymap?,kmod?,selinux?,static-libs?] required by (virtual/udev-197-r2::gentoo, ebuild scheduled for merge)
gnome-base/gvfs:0
(gnome-base/gvfs-1.14.2::gentoo, ebuild scheduled for merge) pulled in by
>=gnome-base/gvfs-1.10.1[udisks,udev] required by (xfce-base/thunar-1.4.0::gentoo, ebuild scheduled for merge)
(gnome-base/gvfs-1.12.3-r1::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
dev-libs/glib:2
(dev-libs/glib-2.32.4-r1::gentoo, installed) pulled in by
<dev-libs/glib-2.33:2 required by (dev-libs/gobject-introspection-1.32.1::gentoo, installed)
(dev-libs/glib-2.34.3::gentoo, ebuild scheduled for merge) pulled in by
>=dev-libs/glib-2.33.12:2 required by (gnome-base/gvfs-1.14.2::gentoo, ebuild scheduled for merge)
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.Is this a problem with the quality control of the ebuilds in some of the packages?
Is this a matter of some aspect of the approach Gentoo is taking I don't understand? If so, I would like to understand it, and also I would like to see it called out more clearly in the documentation.
Here is my make.conf file:
Code: Select all
merom ~ # cat /etc/portage/make.conf
CFLAGS="-O2 -pipe -march=core2"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j3"
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST="x86_64-pc-linux-gnu"
PORTAGE_TMPDIR="/tmp"
# These are the USE flags that were used in addition to what is provided by the
# profile used for building.
USE="
X \
mmx sse sse2 sse3 ssse3 \
keymap \
-gnome -kde -minimal -qt4 dbus jpeg lock session startup-notification thunar udev \
### alsa \
"
INPUT_DEVICES="evdev synaptics"
VIDEO_CARDS="intel"
###GENTOO_MIRRORS="ftp://mirror.mcs.anl.gov/pub/gentoo/ ftp://ftp.gtlib.gatech.edu/pub/gentoo http://gentoo.osuosl.org/"
GENTOO_MIRRORS="ftp://ftp.iinet.net.au/linux/Gentoo/ ftp://ftp.swin.edu.au/gentoo http://gentoo.osuosl.org/"
SYNC="rsync://rsync.au.gentoo.org/gentoo-portage"Thanks,
Bret
