I have emerge sync running as a cron job lately it has not been updating the metadata properly. or maybe at all whenever I go to do an emerge -avuD world it hangs forever emerge --metadata fixes my problem. has portage removed building metadata from sync? or is this a bug?
*** Bug 136143 has been marked as a duplicate of this bug. ***
You didn't post emerge --info output.
(In reply to comment #2) > You didn't post emerge --info output. > I'll make the note that portage was synced on rc4-r4 when I posted last night... Portage 2.1_rc4-r5 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r3, 2.6.16-gentoo-r9 i686) ================================================================= System uname: 2.6.16-gentoo-r9 i686 AMD Athlon(tm) XP 2200+ Gentoo Base System version 1.6.14 ccache version 2.3 [enabled] dev-lang/python: 2.4.2 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-r1 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="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon-xp -pipe -mmmx -m3dnow -msse -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/splash /etc/terminfo" CXXFLAGS="-O2 -march=athlon-xp -pipe -mmmx -m3dnow -msse -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache 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="3dnow 3dnowext X aac alsa apache2 apm avi bash-completion berkdb bitmap-fonts bluetooth cdr clamav cli crypt cups dri dvd dvdread eds emboss encode esd foomaticdb fortran ftp gdbm gif gimp gimp-print gimpprint gpm gtk gtk2 imagemagick imlib isdnlog java javascript jpeg kerberos libg++ libwww logrotate mad math mikmod mmx mmxext motif mp3 mpeg mplayer musicbrainz mysql ncurses nls nptl ogg opengl pam pcre pdflib perl png ppds pppd python qt quicktime readline reflection samba scanner sdk sdl session sockets spell spl sse ssl symlink tcpd theora truetype truetype-fonts type1-fonts udev usb vorbis win32codecs wxwindows x86 xine xml xmms xorg xv zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux userland_GNU video_cards_radeon" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #3) > (In reply to comment #2) > > You didn't post emerge --info output. > > > > I'll make the note that portage was synced on rc4-r4 when I posted last > night... > Haha, hey Caleb, you are on the Lansing GLUUG list ;) Do you have anything in /etc/portage/modules/ ?
This is strange. I've just tested with portage-2.1 final and it seems to work normally. After the sync, it did the metadata transfer: >>> Updating Portage cache: 100% Do you receive a message like that when you sync? The metadata-transfer can be disabled in FEATURES, but I see that you have it enabled...
nothing in /etc/portage/modules directory doesn't exist. It seems to work if I run emerge sync as a command but not as a cron job. crontab is 0 0 * * * /usr/bin/emerge --sync anything wrong with that? maybe it's fine in final I'll check tonight. I just updated it...
Can you direct the output of your cron job to a log file so we can see if anything interesting comes out? If there's nothing interesting there, can you use `find /var/cache/edb/dep/usr/portage` to get a recursive file listing before and after the cron job, just to verify that the cache was untouched?
I think resolved in 2.1