Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Installing XFCE results in slot conflict
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 128

PostPosted: Wed Jan 23, 2013 10:51 pm    Post subject: Installing XFCE results in slot conflict Reply with quote

Having just completed the installation I have gotten xorg to install, then struggled for some days with installing XFCE.

I have tried to follow several guides, the latest one is http://wiki.gentoo.org/wiki/Xfce

Using the command:

emerge --ask xfce4-meta xfce4-notifyd

I now get the following errors:

Code:

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

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)

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-171::gentoo, ebuild scheduled for merge) pulled in by
    =virtual/udev-171[gudev] required by (xfce-base/thunar-1.4.0::gentoo, ebuild scheduled for merge)
    (and 11 more with the same problem)

  (virtual/udev-197::gentoo, ebuild scheduled for merge) pulled in by
    >=virtual/udev-197 required by (sys-fs/udev-197-r3::gentoo, ebuild scheduled for merge)
    (and 2 more with the same problem)

sys-fs/udev:0

  (sys-fs/udev-197-r3::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-197-r3[gudev?,hwdb?,introspection?,keymap?,selinux?,static-libs?] required by (virtual/udev-197::gentoo, ebuild scheduled for merge)

  (sys-fs/udev-171-r9::gentoo, ebuild scheduled for merge) pulled in by
    ~sys-fs/udev-171[gudev?,hwdb?,introspection?,keymap?,selinux?] required by (virtual/udev-171::gentoo, ebuild scheduled for merge)

sys-apps/hwids:0

  (sys-apps/hwids-20121119::gentoo, installed) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (sys-apps/hwids-20130114::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-apps/hwids-20121202.2[udev] required by (sys-fs/udev-197-r3::gentoo, ebuild scheduled for merge)

...

!!! The following installed packages are masked:
- sys-apps/policycoreutils-2.1.13-r5::gentoo (masked by: package.mask)
/usr/portage/profiles/base/package.mask:
# Diego E. Pettenò <flameeyes@gentoo.org> (25 Apr 2010)
#  on behalf of QA team <qa@gentoo.org
#
# Mask SElinux packages on all the profile and unmask it only for
# selinux itself; automagic dependencies can break systems otherwise
#
# Please keep this mask in sync between profiles/package.mask and
# selinux/package.mask (with - prefix there).

- sys-libs/libsemanage-2.1.9::gentoo (masked by: package.mask)
- sec-policy/selinux-xserver-2.20120725-r9::gentoo (masked by: package.mask)
- sys-libs/libselinux-2.1.12-r2::gentoo (masked by: package.mask)
- dev-python/sepolgen-1.1.8::gentoo (masked by: package.mask)
- app-admin/setools-3.3.7-r6::gentoo (masked by: package.mask)
- sec-policy/selinux-base-policy-2.20120725-r10::gentoo (masked by: package.mask)
- sys-libs/libsepol-2.1.8-r1::gentoo (masked by: package.mask)
- sec-policy/selinux-base-2.20120725-r10::gentoo (masked by: package.mask)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.


make.conf:

Code:

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
CFLAGS="-O2 -march=athlon-xp -pipe"
CXXFLAGS="${CFLAGS}"
# 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="i686-pc-linux-gnu"
# These are the USE flags that were used in addition to what is provided by the
# profile used for building.
USE="bindist"

GENTOO_MIRRORS="http://ftp.df.lth.se/pub/gentoo/ rsync://ftp.df.lth.se/pub/gentoo/ ftp://ftp.df.lth.se/pub/gentoo/"

SYNC="rsync://rsync5.se.gentoo.org/gentoo-portage"

USE="-gnome -kde -minimal -qt4 dbus jpeg lock session startup-notification thunar udev X consolekit policykit hwdb udisks"
#USE="xorg udev libkms gtk gnome alsa python -kde"
#USE="-xorg udev libkms gtk gnome alsa python -kde"

INPUT_DEVICES="evdev"
VIDEO_CARDS="radeon"
USE="${USE} -qt4"


package.use:

Code:

x11-base/xorg-server udev
#required by sys-auth/polkit-0.107-r1[pam], required by sys-power/upower-0.9.18, required by xfce-base/xfce4-session-4.10.0[udev], required by xfce-base/xfce4-meta-4.10, required by xfce4-meta (argument)
=sys-auth/pambase-20101024-r2 consolekit
#required by sys-auth/polkit-0.110, required by sys-fs/udisks-2.0.91, required by gnome-base/gvfs-1.14.2[udisks], 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)
>=sys-auth/consolekit-0.4.5_p20120320-r1 policykit
#required by virtual/udev-197, required by sys-fs/udev-init-scripts-19
=sys-fs/udev-197-r3 gudev hwdb
#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 udisks
#required by gnome-base/gvfs-1.14.2[udev], 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)
=virtual/udev-171 gudev
#required by sys-fs/udisks-2.0.91, required by gnome-base/gvfs-1.14.2[udisks], 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)
>=virtual/udev-197 gudev hwdb
#required by virtual/udev-171, 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)
=sys-fs/udev-171-r9 gudev
app-text/poppler -qt4
dev-util/cmake -qt4
gnome-base/gvfs -http


How do I resolve this problem so that I can install XFCE?
Back to top
View user's profile Send private message
jburns
l33t
l33t


Joined: 18 Jan 2007
Posts: 783
Location: Massachusetts USA

PostPosted: Wed Jan 23, 2013 11:33 pm    Post subject: Reply with quote

It looks like you are trying to mix stable and unstable packages. You should try building either all stable or all unstable.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 128

PostPosted: Wed Jan 23, 2013 11:38 pm    Post subject: Reply with quote

jburns wrote:
It looks like you are trying to mix stable and unstable packages. You should try building either all stable or all unstable.


Thanks, how do I specify all packages to be built stable?
Back to top
View user's profile Send private message
jburns
l33t
l33t


Joined: 18 Jan 2007
Posts: 783
Location: Massachusetts USA

PostPosted: Wed Jan 23, 2013 11:58 pm    Post subject: Reply with quote

Normally there is ACCEPT_KEYWORDS="xxx" in /etc/make.conf. Where xxx is the system type. I did not see that in your file. The question is how are you specifying the unstable packages. It could be in /etc/portage/package.accept_keywords or /etc/portage/package.keywords. Execute "man portage" for more information.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6254
Location: Goose Creek SC

PostPosted: Thu Jan 24, 2013 12:32 am    Post subject: Reply with quote

In /etc/portage/make.conf (or in /etc/make.conf if not yet updated to the new location) either no ACCEPT_KEYWORDS= or ACCEPT_KEYWORDS="amd64" (global) will cause all emerged packages to be stable branch unless otherwise specified. If your arch is not amd64 substitute your arch title. You can specify other keywords on a per emerge or a per package basis. http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?style=printable&full=1 sections Working with Gentoo and Working with Portage refer.

suggest
Code:
emerge --sync
emerge -uND world
revdep-rebuild


portage discrepancies:
glib-2.33 does not exist in database
glib-2.33.12 does not exist in database
glib-2.34.3 hard masked and not keyworded

are you using an overlay?
_________________
Defund the FCC.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 128

PostPosted: Thu Jan 24, 2013 1:29 am    Post subject: Reply with quote

DONAHUE wrote:
In /etc/portage/make.conf (or in /etc/make.conf if not yet updated to the new location) either no ACCEPT_KEYWORDS= or ACCEPT_KEYWORDS="amd64" (global) will cause all emerged packages to be stable branch unless otherwise specified. If your arch is not amd64 substitute your arch title. You can specify other keywords on a per emerge or a per package basis. http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?style=printable&full=1 sections Working with Gentoo and Working with Portage refer.

suggest
Code:
emerge --sync
emerge -uND world
revdep-rebuild


portage discrepancies:
glib-2.33 does not exist in database
glib-2.33.12 does not exist in database
glib-2.34.3 hard masked and not keyworded

are you using an overlay?


What architectures are available? This is an old AMD Athlon XP, for GCC's march argument I'm using "athlon-xp". However I'm guessing I can't use that, perhaps "i386" or "x86"?

I'm not using an overlay.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6254
Location: Goose Creek SC

PostPosted: Thu Jan 24, 2013 1:59 am    Post subject: Reply with quote

arch or architecture tends to have multiple meanings

AMD Athlon XP should be keyworded x86 and will be correctly defaulted if you leave ACCEPT_KEYWORDS out of /etc/portage/make.conf (/etc/make.conf). This is used by portage in selecting package versions.

gcc's -march is more specific. http://en.gentoo-wiki.com/wiki/Safe_Cflags/AMD#Athlon_XP.2FGeode_NX refers. However that page is out of date a bit;
Quote:
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CXXFLAGS="${CFLAGS}"
would be my choice. -march=native allows gcc to pick optimal processor flags. They will likely be the same as -march=athlon-4 would choose but
_________________
Defund the FCC.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 128

PostPosted: Fri Jan 25, 2013 6:34 am    Post subject: Reply with quote

DONAHUE wrote:
In /etc/portage/make.conf (or in /etc/make.conf if not yet updated to the new location) either no ACCEPT_KEYWORDS= or ACCEPT_KEYWORDS="amd64" (global) will cause all emerged packages to be stable branch unless otherwise specified. If your arch is not amd64 substitute your arch title. You can specify other keywords on a per emerge or a per package basis. http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?style=printable&full=1 sections Working with Gentoo and Working with Portage refer.

suggest
Code:
emerge --sync
emerge -uND world
revdep-rebuild


portage discrepancies:
glib-2.33 does not exist in database
glib-2.33.12 does not exist in database
glib-2.34.3 hard masked and not keyworded

are you using an overlay?


I tried this now, eventually I get:

Code:

make[3]: *** [matmul_i8.lo] Error 1
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.6.3/work/build/i686-pc-linux-gnu/libgfortran'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.6.3/work/build/i686-pc-linux-gnu/libgfortran'
make[1]: *** [all-target-libgfortran] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
 * ERROR: sys-devel/gcc-4.6.3 failed (compile phase):
 *   emake failed with bootstrap-lean
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 4035:  Called toolchain_src_compile
 *   environment, line 4695:  Called gcc_do_make
 *   environment, line 2346:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
 *
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.6.3'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.6.3'`.
 *
 * Please include /var/tmp/portage/sys-devel/gcc-4.6.3/work/build/gcc-build-logs.tar.bz2 in your bug report
 *
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'

>>> Failed to emerge sys-devel/gcc-4.6.3, Log file:

>>>  '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/build.log'

 * Messages for package net-mail/mailbase-1.1:

 * Your //var/spool/mail/ directory permissions differ from
 *   those which mailbase wants to set it to (03775).
 *   If you did not change them on purpose, consider running:
 *
 *     chown root:mail //var/spool/mail/
 *     chmod 03775 //var/spool/mail/

 * Messages for package app-text/libpaper-1.1.24-r1:

 * run "paperconf -p letter" as root to use letter-pagesizes
 * or paperconf with normal user privileges.

 * Messages for package sys-devel/gcc-4.6.3:

 *
 * LTO support is still experimental and unstable.
 * Any bugs resulting from the use of LTO will not be fixed.
 *
 * ERROR: sys-devel/gcc-4.6.3 failed (compile phase):
 *   emake failed with bootstrap-lean
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 4035:  Called toolchain_src_compile
 *   environment, line 4695:  Called gcc_do_make
 *   environment, line 2346:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBCFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TAR
 *
 * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.6.3'`,
 * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.6.3'`.
 *
 * Please include /var/tmp/portage/sys-devel/gcc-4.6.3/work/build/gcc-build-logs.tar bug report
 *
 * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/temp/
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.6.3/ment'.
 * Working directory: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'
 * S: '/var/tmp/portage/sys-devel/gcc-4.6.3/work/build'
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6254
Location: Goose Creek SC

PostPosted: Fri Jan 25, 2013 5:48 pm    Post subject: Reply with quote

Code:
gcc-config -l
gcc-config {latest version on list}
gcc-config -l
gcc-config {latest version on list}
env-update && source /etc/profile
emerge --oneshot libtool


then try
Code:
emerge --sync
emerge -uND --keep-going world
revdep-rebuild
which should bypass the gcc-4.6.3 emerge if it fails again

or

Code:
echo ">sys-devel/gcc-4.5.4" >> /etc/portage/package.mask
emerge --sync
emerge -uND --keep-going world
gcc-config -l
gcc-config {latest version on list}
env-update && source /etc/profile
emerge --oneshot libtool
revdep-rebuild
which should hold gcc at version 4.5.4 until you remove the entry in package.mask

or

Code:
emerge --sync
echo "=sys-devel/gcc-4.7.2 ~x86" >> /etc/portage/package.keywords
echo "=sys-devel/gcc-4.7.2" >> /etc/portage/package.unmask
emerge -uND --keep-going world
gcc-config -l
gcc-config {latest version on list}
env-update && source /etc/profile
emerge --oneshot libtool
revdep-rebuild
which should emerge the latest testing branch version which may be fixed
_________________
Defund the FCC.
Back to top
View user's profile Send private message
deltamalloc
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2013
Posts: 128

PostPosted: Sun Jan 27, 2013 11:09 pm    Post subject: Reply with quote

DONAHUE wrote:
Code:
gcc-config -l
gcc-config {latest version on list}
gcc-config -l
gcc-config {latest version on list}
env-update && source /etc/profile
emerge --oneshot libtool


then try
Code:
emerge --sync
emerge -uND --keep-going world
revdep-rebuild
which should bypass the gcc-4.6.3 emerge if it fails again

or

Code:
echo ">sys-devel/gcc-4.5.4" >> /etc/portage/package.mask
emerge --sync
emerge -uND --keep-going world
gcc-config -l
gcc-config {latest version on list}
env-update && source /etc/profile
emerge --oneshot libtool
revdep-rebuild
which should hold gcc at version 4.5.4 until you remove the entry in package.mask

or

Code:
emerge --sync
echo "=sys-devel/gcc-4.7.2 ~x86" >> /etc/portage/package.keywords
echo "=sys-devel/gcc-4.7.2" >> /etc/portage/package.unmask
emerge -uND --keep-going world
gcc-config -l
gcc-config {latest version on list}
env-update && source /etc/profile
emerge --oneshot libtool
revdep-rebuild
which should emerge the latest testing branch version which may be fixed


Thank you for the help. However I ended up just reinstalling Gentoo and selecting "desktop" this time, last time I had selected "selinux".

I still got the slot conflict though, then I added ACCEPT_KEYWORDS="x86" and performed the steps you had specified in that related post.

This actually worked and installed XFCE.

I'm a little curious though. Why does the install guide not specify to add ACCEPT_KEYWORDS as part of the installation procedure? Is it desired that normal Gentoo users compile and use unstable code? Also how and why does "ACCEPT_KEYWORDS" prevent unstable packages from being built?
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 6254
Location: Goose Creek SC

PostPosted: Mon Jan 28, 2013 5:31 am    Post subject: Reply with quote

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?style=printable&full=1 The sections Working with Gentoo and Working with Portage are recommended reading.
when you installed the x86 stage3, x86 was installed as the default keyword. Placing ACCEPT_KEYWORDS="x86" in /etc/portage/make.conf would be a harmless redundancy.
in /etc/portage you can specify ACCEPT_KEYWORDS="~amd64" which would cause ~x86 packages to be built whenever such a package is the latest version of any ebuild
in /etc/portage//package.keywords you can specify individual ~x86 packages to be built as you did for gcc
packages placed in the testing branch are there in hopes that many users will try them and report bugs and fixes before they graduate to stable.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
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