attempting to upgrade from xorg-x11-6.8.2-r7 currently installed, the -r8 version appears to relink /usr/lib64 from 'lib' to '../lib64', which breaks python midway through the installation, which leaves portage in an unusable state. (emerge/python will then fail the following errors, for those searching for similar troubles: Could not find platform dependent libraries <exec_prefix> ImportError: No module named fcntl ) Portage 2.1-r1 (default-linux/amd64/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.15-gentoo-r7 x86_64) ================================================================= System uname: 2.6.15-gentoo-r7 x86_64 AMD Opteron(tm) Processor 142 Gentoo Base System version 1.6.15 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5-r2, 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] 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-r2 sys-devel/gcc-config: 1.3.13-r2 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="-O3 -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/lib/X11/xkb /usr/share/config /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" MAKEOPTS="-j2" 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" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac acl alsa apache2 audiofile avi bcmath berkdb bitmap-fonts bzip2 bzlib calendar cdb cli crypt cups curl dba dbm dio divx4linux dri dvb dvd eds emboss encode exif fam fastcgi fftw flac flatfile foomaticdb fortran gd gdbm gif gmp gnome gpm gstreamer gtk gtk2 howl iconv imagemagick imap imlib iproute2 ipv6 isdnlog jabber jpeg kde kerberos lcms ldap lua lzw lzw-tiff maildir mcal mhash mmap mng mp3 mpeg mysql ncurses nls nodrm nptl nptlonly offensive ogg oggvorbis opengl pam pcntl pcre pdflib perl php pie png posix pppd python qt qt3 qt4 quicktime readline recode reflection rrdtool samba sasl sdl session shared sharedmem sndfile snmp soap sockets speex spell spl sqlite ssl svg sysvipc tcltk tcpd tiff truetype truetype-fonts type1-fonts unicode usb utf8 vorbis webdav xattr xface xorg xpm xsl xv xvid zlib elibc_glibc kernel_linux userland_GNU" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS
*** This bug has been marked as a duplicate of 132135 ***
i didn't understand your emerge comment, now i do. I didn't type 'emerge -snoname' as the command. This is what i typed and saw: ===== root@randomaccess /home/rmunsch # revdep-rebuild -soname libldap-2.2.so.7 Configuring search environment for revdep-rebuild Environment mismatch from previous run, deleting temporary files... Checking reverse dependencies... Packages containing binaries and libraries broken by a package update will be emerged. Collecting system binaries and libraries... done. (/root/.revdep-rebuild.1_files) Collecting complete LD_LIBRARY_PATH... done. (/root/.revdep-rebuild.2_ldpath) Checking dynamic linking consistency... broken /usr/bin/b2m (requires libldap-2.2.so.7) broken /usr/bin/ctags (requires libldap-2.2.so.7) ..... (list about 50 more things) ..... broken /usr/libexec/evolution-webcal (requires libsoup-2.2.so.7) done. (/root/.revdep-rebuild.3_rebuild) Assigning files to ebuilds... done. (/root/.revdep-rebuild.4_ebuilds) Evaluating package order... Warning: Failed to resolve package order. Will merge in "random" order! Possible reasons: - An ebuild is no longer in the portage tree. - An ebuild is masked, use /etc/portage/packages.keyword and/or /etc/portage/package.unmask to unmask it ..... done. (/root/.revdep-rebuild.5_order) All prepared. Starting rebuild... emerge --oneshot -soname libldap-2.2.so.7 =app-admin/sudo-1.6.8_p9-r2 =app-cdr/k3b-0.12.8 =app-editors/xemacs-21.4.15-r3 =app-office/openoffice-2.0.1 =app-text/poppler-bindings-0.5.0 =dev-php/mod_php-4.4.0-r9 =dev-php/php-4.4.0-r4 =dev-util/subversion-1.2.3-r2 =gnome-base/gconf-2.12.1 =gnome-base/gnome-volume-manager-1.2.2 =gnome-extra/evolution-webcal-2.2.1 =gnome-extra/gnome-media-2.10.2 =gnome-extra/gnome-utils-2.10.1-r1 =gnome-extra/nautilus-cd-burner-2.10.2 =kde-base/kdebase-3.4.3-r1 =kde-base/kdemultimedia-3.4.3 =mail-client/evolution-2.2.3-r3 =media-libs/flac-1.1.2-r3 =media-libs/tunepimp-0.3.0-r1 =media-libs/xine-lib-1.0.1-r4 =media-plugins/gst-plugins-flac-0.8.8 =media-sound/alsaplayer-0.99.76 =media-sound/vorbis-tools-1.0.1 =www-client/epiphany-1.6.4 .......... !!! Error: -m is an invalid short action or option. revdep-rebuild failed to emerge all packages # ====== the 'emerge --soneshot -soname' command was, i guess, carried over automatically by the system (i didn't type it) because of my "revdep-rebuild -soname" with one dash instead of two. But STILL... none of this explains, or fixes, going from emerge openldap to omgwtf everything's broken and complaining, frex thusly: rmunsch@randomaccess ~ $ svn svn: error while loading shared libraries: libldap-2.2.so.7: cannot open shared object file: No such file or directory
gnnnn.. the above was being entered as, apparently, this was being merged.
(In reply to comment #2) > i didn't understand your emerge comment, now i do. I didn't type 'emerge > -snoname' as the command. This is what i typed and saw: You are posting to a wrong bug again. This has nothing to do with your LDAP issue.
(In reply to comment #4) > (In reply to comment #2) > > i didn't understand your emerge comment, now i do. I didn't type 'emerge > > -snoname' as the command. This is what i typed and saw: > > You are posting to a wrong bug again. This has nothing to do with your LDAP > issue. > I couldn't agree more. why did it get merged here then? I clicked the link in my notification email and here got sent. this has been a very frustrating day.
