Bug 141850 – dev-ruby/log4r collisions in /usr/lib64/ruby/gems...

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Patrick Hahn 2006-07-26 21:41:50 UTC]

Lots of collisions here.  Relavent output of emerge command is attached.

package dev-ruby/log4r-1.0.5 NOT merged

$ emerge --info
Portage 2.1.1_pre3-r5 (default-linux/amd64/2006.0, gcc-3.4.6, glibc-2.4-r3, 2.6.16-beyond4 x86_64)
=================================================================
System uname: 2.6.16-beyond4 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.12.1
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.3 [enabled]
app-admin/eselect-compiler: [Not Present]
dev-lang/python:     2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.3
dev-util/confcache:  0.4.2-r1
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo"
CXXFLAGS="-march=athlon64 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache collision-protect confcache distlocks metadata-transfer parallel-fetch sandbox sfperms strict userfetch userpriv usersandbox"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LANG="en_US.utf8"
LC_ALL="en_US.utf8"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/portage/local/layman/break-my-gentoo-main /usr/portage/local/layman/science /usr/portage/local/layman/gentoo-de /usr/portage/local/layman/break-my-gentoo-main /usr/portage/local/layman/science /usr/portage/local/layman/gentoo-de"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X acpi alsa avi bash-completion berkdb bitmap-fonts bzip2 cjk cli crosscompile crypt cups dlloader doc dri dts eds emboss encode exif expat fam fastcgi firefox flac font-server foomaticdb fortran fuse gdbm gif gimp glep glut gnome gpm gstreamer gtk gtk2 hal idn imagemagick imlib ipv6 isdnlog java jpeg kde lcms lm_sensors lzw lzw-tiff mad mng motif mozilla mp3 mpeg mysql ncurses nls nptl nptlonly ntfs nvidia ogg oggvorbis opengl oss pam pcre pdf pdflib perl pic png postgres pppd python qt qt3 qt4 quicktime readline realtcgi reflection ruby samba sdl session silc slang sox spell spl sqlite ssl svg tcltk tcpd tetex threads tiff truetype truetype-fonts type1-fonts unicode usb utf8 vorbis xinerama xml2 xorg xpm xv zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux userland_GNU"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS

[Comment 1 Patrick Hahn 2006-07-26 21:42:30 UTC]

Created attachment 92825 [details]
output of emerge -q --nospinner dev-ruby/log4r

[Comment 2 Diego Elio Pettenò (RETIRED) 2006-07-26 23:30:21 UTC]

Is this an update/rebuild? If so, it might just be fixing up for amd64 lib64 path.
If it's a new install, who owns that files currently?

[Comment 3 Patrick Hahn 2006-07-27 06:51:01 UTC]

It was a new install. Unfortunately, I disabled collision-protect and emerged over the collisions. Rebuilding it didn't run into any collisions, I probably had a manually installed gem. Sorry about that.