Bug 160893 – Portage 2.1.1-r2 emerge --sync cache update error

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Matthew Schultz 2007-01-08 14:27:11 UTC]

I just got an error this morning when I did an emerge --sync when it was updating the cache:

>>> Updating Portage cache:   99%Traceback (most recent call last):
  File "/usr/bin/emerge", line 4049, in ?
    emerge_main()
  File "/usr/bin/emerge", line 4006, in emerge_main
    action_sync(settings, trees, mtimedb, myopts, myaction)
  File "/usr/bin/emerge", line 2924, in action_sync
    action_metadata(settings, portdb, myopts)
  File "/usr/bin/emerge", line 3019, in action_metadata
    eclass_cache=ec, verbose_instance=noise_maker)
  File "/usr/lib/portage/pym/cache/util.py", line 99, in mirror_cache
    try:        del trg_cache[key]
  File "/usr/lib/portage/pym/cache/template.py", line 81, in __delitem__
    self._delitem(cpv)
  File "/usr/lib/portage/pym/cache/flat_hash.py", line 105, in _delitem
    raise KeyError(cpv)
KeyError: 'dev-lang/prothon-0.1.2_p711'


emerge --info

Portage 2.1.1-r2 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.4-r4, 2.6.19-gentoo-r2 x86_64)
=================================================================
System uname: 2.6.19-gentoo-r2 x86_64 Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
Gentoo Base System version 1.12.6
Last Sync: Mon, 08 Jan 2007 14:00:03 +0000
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python:     2.4.3-r4
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.61
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.14
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=nocona -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-march=nocona -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer parallel-fetch sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.cites.uiuc.edu/pub/gentoo/ http://gentoo.mirrors.easynews.com/linux/gentoo/ http://mirror.phy.olemiss.edu/mirror/gentoo"
LINGUAS="en ru"
MAKEOPTS="-j3"
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 a52 aac adns alsa alsa_cards_ali5451 alsa_cards_als4000 alsa_cards_atiixp alsa_cards_atiixp-modem alsa_cards_bt87x alsa_cards_ca0106 alsa_cards_cmipci alsa_cards_emu10k1x alsa_cards_ens1370 alsa_cards_ens1371 alsa_cards_es1938 alsa_cards_es1968 alsa_cards_fm801 alsa_cards_hda-intel alsa_cards_intel8x0 alsa_cards_intel8x0m alsa_cards_maestro3 alsa_cards_trident alsa_cards_usb-audio alsa_cards_via82xx alsa_cards_via82xx-modem alsa_cards_ymfpci alsa_pcm_plugins_adpcm alsa_pcm_plugins_alaw alsa_pcm_plugins_asym alsa_pcm_plugins_copy alsa_pcm_plugins_dmix alsa_pcm_plugins_dshare alsa_pcm_plugins_dsnoop alsa_pcm_plugins_empty alsa_pcm_plugins_extplug alsa_pcm_plugins_file alsa_pcm_plugins_hooks alsa_pcm_plugins_iec958 alsa_pcm_plugins_ioplug alsa_pcm_plugins_ladspa alsa_pcm_plugins_lfloat alsa_pcm_plugins_linear alsa_pcm_plugins_meter alsa_pcm_plugins_mulaw alsa_pcm_plugins_multi alsa_pcm_plugins_null alsa_pcm_plugins_plug alsa_pcm_plugins_rate alsa_pcm_plugins_route alsa_pcm_plugins_share alsa_pcm_plugins_shm alsa_pcm_plugins_softvol apache2 audiofile avi bcmath bdf berkdb bitmap-fonts bzip2 calendar cdr cjk clamav cli cracklib crypt ctype cups curl curlwrappers dbus dio directfb dlloader dri dts dvb dvd dvdread elibc_glibc emu-linux-x86 encode exif fbcon ffmpeg flac fortran ftp gd gdbm gif gmp gpm gtk gtk2 hal hardenedphp hash iconv ieee1394 imagemagick imap imlib innodb input_devices_keyboard input_devices_mouse ipv6 isdnlog ithreads java javascript jpeg jpeg2k kde kernel_linux lcms ldap libg++ linguas_en linguas_ru logrotate lzo mad matroska mcal mhash mime mjpeg mng mp3 mp4 mpeg msession msn mysql mysqli ncurses network nls nptl nptlonly nsplugin nvidia ogg openal opengl osc oss pam pcntl pcre pdf pdo pear perl php png posix postgres ppds pppd python qt qt3 qt4 quicktime readline reflection samba sasl sdl seamonkey session simplexml snmp soap sockets spl sqlite ssl subversion svg tcpd theora threads tidy tiff tokenizer transcode truetype truetype-fonts type1-fonts udev unicode usb userland_GNU v4l v4l2 vcd video_cards_fbdev video_cards_nv video_cards_nvidia video_cards_v4l video_cards_vesa vorbis wddx wifi wxwindows x264 xine xml xorg xpm xv xvid zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS

[Comment 1 Zac Medico 2007-01-08 16:24:45 UTC]

Did you have a second emerge instance running at the same time?  Normally, a cache entry won't suddenly disappear like that.  Anyway, I've fixed it to ignore that in svn r5483.

If you run `emerge --metadata` does it complete normally?  It's possible that some kind of corruption could have triggered the error.

[Comment 2 Matthew Schultz 2007-01-08 16:38:46 UTC]

emerge --metadata and --sync seem to working fine now.  I believe I might have been running emerge while I was doing a sync at the time.

[Comment 3 Matthew Schultz 2007-01-08 16:41:00 UTC]

Is running emerge on a package while doing a sync supported behavior?

[Comment 4 Andrew Gaffney (RETIRED) 2007-01-08 16:44:57 UTC]

Heh, no. Portage would get...uppity if an ebuild it was planning on using suddenly disappears out from under it.

[Comment 5 Matthew Schultz 2007-01-08 16:57:05 UTC]

Perhaps this bug should turn into an enhancement?  emerging packages should be disabled or pause until emerge --sync has completed.  Likewise, if an emerging a package is in progress, then emerge --sync should be disabled or pause until the package emerge has completed.

[Comment 6 Zac Medico 2007-01-08 20:15:21 UTC]

(In reply to comment #5)
> Perhaps this bug should turn into an enhancement?  emerging packages should be
> disabled or pause until emerge --sync has completed.  Likewise, if an emerging
> a package is in progress, then emerge --sync should be disabled or pause until
> the package emerge has completed.

Parallel emerge instances will work in many cases but that behavior is completely unsupported for the time being.  We already have bug #147516 so there's no need for another.  Anyway, the particular error that you triggered is fixed now.

[Comment 7 Matthew Schultz 2007-01-08 20:41:20 UTC]

I didn't realize a bug was already filed for it.  Thanks for fixing the problem.

[Comment 8 Zac Medico 2007-01-11 04:15:47 UTC]

This has been released in 2.1.2_rc4-r8.