Bug 127903 – after upgrading to 2.1pre7-r2 updating cache fails

• Status: RESOLVED INVALID
• Product: Portage Development

[Description Dariusz Gadomski 2006-03-28 13:10:53 UTC]

I've made an attempt to upgrade portage from 2.0.54 to 2.1pre7-r2. As the information told me I executed emerge --metadata.
I get over 47 000 lines of errors like this:

Failed cache update: xfce-extra/xfmedia-0.9.1 aux_get() got an unexpected keyword argument 'metacachedir'
100%
Failed cache update: xfce-extra/xfwm4-themes-4.2.3 aux_get() got an unexpected keyword argument 'metacachedir'

I believe most of the ebuilds are mentioned.

I've made several syncs (nad webrsyncs), it didn't help.
Downgrading to 2.0.54 makes the problem disappear.

My emerge --info:
Portage 2.1_pre7-r2 (default-linux/amd64/2005.1, gcc-3.4.6, glibc-2.4-r1, 2.6.15-gentoo-r1 x86_64)
=================================================================
System uname: 2.6.15-gentoo-r1 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.12.0_pre16
dev-lang/python:     2.3.5, 2.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-r2
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=k8 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O2 -march=k8 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://mirror.gentoo.no http://gentoo.prz.rzeszow.pl http://gentoo.po.opole.pl ftp://gentoo.po.opole.pl "
LDFLAGS="-Wl,-z,now"
LINGUAS="pl en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="amd64 X alsa arts avi berkdb bitmap-fonts crypt cups dri eds emboss encode eps foomaticdb fortran gif gpm gstreamer gtk gtk2 imlib ipv6 jpeg kde lame libwww lzw lzw-tiff mitshm motif mp3 mpeg ncurses nls nptl nptlonly ogg oggvorbis opengl pam pdflib perl png python qt quicktime readline sdl slang spell ssl tcpd threads tiff truetype truetype-fonts type1-fonts usb vorbis xpm xv zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_pl linguas_en userland_GNU video_cards_ati"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL

[Comment 1 Zac Medico 2006-03-29 01:03:05 UTC]

It seems that /usr/bin/emerge did not update.  It should be a symlink to /lib/portage/bin/emerge.  Maybe you only need to create the symlink, like this:

rm -f /usr/bin/emerge
ln -s /lib/portage/bin/emerge /usr/bin/emerge

[Comment 2 Marius Mauch (RETIRED) 2006-03-29 03:55:42 UTC]

That should be /usr/lib/portage/bin of course

[Comment 3 Dariusz Gadomski 2006-03-29 04:15:48 UTC]

> rm -f /usr/bin/emerge
> ln -s /usr/lib/portage/bin/emerge /usr/bin/emerge

I've just done that but unfortunately cache update is still broken :(

[Comment 4 Simon Stelling (RETIRED) 2006-05-02 10:09:51 UTC]

Can you still reproduce this with a newer 2.1pre? I've once hit that too and figured out that i was using an old 'emerge' with a newer portage because I used some nasty quirks.

[Comment 5 Dariusz Gadomski 2006-05-02 10:23:30 UTC]

> Can you still reproduce this with a newer 2.1pre? 
I'm afraid not. Due to hard drive failure I was forced to install Gentoo once again. I had no problem with 'emerge' on new system.

[Comment 6 Simon Stelling (RETIRED) 2006-05-02 10:57:29 UTC]

there's never been a bug *yedimindtrick*