Summary: | Portage attempts to install many packages (gettext, libXt, libXrender, and maybe more) out of order after xorg-6.8 removed | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Stephen Hicks <kupopo1> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | johan |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Initial output of 'emerge -eav xorg-x11' before manually disentangling depenency problem (problemmatic lines highlighted)
Output with --debug flag. |
Description
Stephen Hicks
2006-08-12 14:40:54 UTC
Created attachment 94093 [details]
Initial output of 'emerge -eav xorg-x11' before manually disentangling depenency problem (problemmatic lines highlighted)
(In reply to comment #0) > while for gettext, I had to keep it (0.14.5 - I already had 0.14.4 installed) > masked until xorg-x11 was complete, and at that point, it installed. Well huh, gettext shouldn't depend on X.org at all, I blame the emacs use flag. Can you attach some error messages from that? I recall the gettext problem was due at least in part to the emacs USE flag, but the libXt and libXrender problems are still there. Something in the dependency tree needs to be fixed so that libX11 and others are installed *before* these libraries that depend on them. I recall the gettext problem was due at least in part to the emacs USE flag, but the libXt and libXrender problems are still there. Something in the dependency tree needs to be fixed so that libX11 and others are installed *before* these libraries that depend on them. Unfortunately, I did not save any of the error messages. Please attach emerge --pretend --debug output for the command that produces the incorrect order. I would if I could, but I can't. I worked around the bug by manually masking some packages (gettext) and installing others before portage wanted to (libX11). Thus, my system is no longer in a state which produces the bug. It seems to me, however, that this is a serious problem and shouldn't be disregarded just because I can't produce any more information. But maybe that intuition is wrong, and if it is a real problem and not just a side effect from something unsafe I may have done ages ago, then somebody else will reopen it. If it's a real problem then somebody else will encounter it and provide the necessary information. Without more information, there's no point in leaving this bug open. I seem to have the same problem. After removing the old xorg-x11 package, i tried to update world: emerge --buildpkg --update --deep world I'll attach a log with --debug enabled. emerge --info: Portage 2.1-r2 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.15-gent oo-r1 i686) ================================================================= System uname: 2.6.15-gentoo-r1 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.6.15 ccache version 2.3 [enabled] app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.3.5-r2, 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 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-r3 sys-devel/gcc-config: 1.3.13-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shu tdown /usr/lib/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=i686" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://devsrv.transmode.se/portage/distfiles http://gentoo.osuos l.org/" LC_ALL="en_US.utf8" LINGUAS="en se" MAKEOPTS="-j2 -s" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/d istfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://devsrv.transmode.se/gentoo-portage" USE="x86 X alsa apache2 apm avi berkdb bitmap-fonts cli crypt cups dlloader dri eds emacs emboss encode firefox foomaticdb fortran gdbm gif gnome gpm gtk gtk2 i mlib ipv6 isdnlog jpeg libg++ libwww mikmod motif mp3 ncurses nls nptl opengl os s pam pcre pdflib perl pic png pppd python qt3 qt4 quicktime readline reflection session spell spl ssl tcpd truetype truetype-fonts type1-fonts udev unicode usb xml xmms xorg xv zlib elibc_glibc input_devices_keyboard input_devices_mouse in put_devices_evdev kernel_linux linguas_en linguas_se userland_GNU" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, PORTAGE_RSYNC _EXTRA_OPTS Created attachment 94442 [details]
Output with --debug flag.
Looks like the emacs installed is linked against X11 but you've removed it. If you run `revdep-rebuild` from gentoolkit it'll probably pick it up. The bigger problem likely can't be fixed without portage tracking link-level dependencies and/or recursively removing revdeps when removing a package. > Looks like the emacs installed is linked against X11 but you've removed it.
I see that now... The problem is that this is what happens when you try to upgrade to the latest stable xorg-x11 and have the emacs use-flag set. revdep-rebuild does not work, as there is a deadlock between gettext, needed by xorg-x11, and emacs. To reinstall gettext, you need a working emacs. To get a working emacs, you need a working gettext...
I'll try changing the emacs use-flag temporarily and recompile emacs to get around this.
I tried disabling the emacs use-flag, but that didn't help, the compilation of gettext still needs emacs. The reason why emacs wouldn't compile was not because of gettext but because of missing xorg-x11. Remerging emacs without X solved the problem. |