Summary: | emerge -k fails, portage 2.0.46-r9 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Arkadi Shishlov <arkadi> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Arkadi Shishlov
2003-02-02 12:21:38 UTC
what exactly are you typing ? `emerge -k <tbz2 file>` ? emerge -k winex or emerge -k prelink what does `ls /usr/portage/packages -R` show ? Symlinks are there for packages created by emerge, no symlinks by quickpkg. Regardless of symlink presence, no package can be installed. For example, I cannot emerge -k gcc-config, same error. /usr/portage/packages: All/ app-text/ media-gfx/ media-libs/ media-sound/ media-video/ net-p2p/ sys-devel/ x11-libs/ x11-misc/ /usr/portage/packages/All: alsa-driver-0.9.0_rc6.tbz2 fontconfig-2.0-r4.tbz2 nvidia-glx-1.0.3123.tbz2 winex-20021123-dbg.tbz2 autoconf-2.57.tbz2 gcc-3.2.1-r7.tbz2 nvidia-kernel-1.0.3123-r2.tbz2 winex-20021123.tbz2 automake-1.7.2.tbz2 gcc-config-1.3.1.tbz2 prelink-20021213.tbz2 binutils-2.13.90.0.18.tbz2 ggv-1.99.97.tbz2 qt-dcgui-0.2.3.tbz2 dclib-0.2.3.tbz2 gqview-1.2.1.tbz2 ttmkfdir-3.0.4.tbz2 /usr/portage/packages/app-text: ggv-1.99.97.tbz2@ /usr/portage/packages/media-gfx: gqview-1.2.1.tbz2@ /usr/portage/packages/media-libs: fontconfig-2.0-r4.tbz2@ /usr/portage/packages/media-sound: alsa-driver-0.9.0_rc6.tbz2@ /usr/portage/packages/media-video: nvidia-kernel-1.0.3123-r2.tbz2@ /usr/portage/packages/net-p2p: dclib-0.2.3.tbz2@ qt-dcgui-0.2.3.tbz2@ /usr/portage/packages/sys-devel: autoconf-2.57.tbz2@ automake-1.7.2.tbz2@ binutils-2.13.90.0.18.tbz2@ gcc-3.2.1-r7.tbz2@ gcc-config-1.3.1.tbz2@ /usr/portage/packages/x11-libs: /usr/portage/packages/x11-misc: ttmkfdir-3.0.4.tbz2@ Remove all the tbz2's and 'emerge -b gcc-config' then try -k again. After clearing /usr/portage/packages emerge -k works again. One of your tarballs is bad... You can try and isolate it... just move it out. db fix db fix |