Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 54380 - Cannot emerge sync after updating to portage-2.0.51_pre10
Summary: Cannot emerge sync after updating to portage-2.0.51_pre10
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2004-06-18 19:11 UTC by Callan Tham
Modified: 2004-07-27 18:41 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
/usr/portage/metadata/timestamp.chk (timestamp.chk,4.00 KB, application/octet-stream)
2004-06-20 07:43 UTC, Callan Tham
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Callan Tham 2004-06-18 19:11:20 UTC
Updated my portage to 2.0.51_pre10, and gentoolkit along with it. Now when I try emerge sync I get a traceback error.

Reproducible: Always
Steps to Reproduce:
1. emerge sync
Actual Results:  
aragorn root # emerge sync
Traceback (most recent call last):
  File "/usr/bin/emerge", line 2158, in ?
    mytimestamp=time.mktime(time.strptime(content[0], "%a, %d %b %Y %H:%M:%S
+0000"))
  File "/usr/lib/python2.3/_strptime.py", line 424, in strptime
    raise ValueError("time data did not match format:  data=%s  fmt=%s" %
ValueError: time data did not match format:  data=<?xml version="1.0"
encoding="utf-8"?>  fmt=%a, %d %b %Y %H:%M:%S +0000

Expected Results:  
Update portage tree

aragorn root # emerge info
Portage 2.0.51_pre10 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r0,
2.4.25-gentoo-r2)
=================================================================
System uname: 2.4.25-gentoo-r2 i686 Intel(R) Pentium(R) III Mobile CPU       800MHz
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
Binutils: sys-devel/binutils-2.14.90.0.8-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer -mmmx -msse -mfpmath=sse"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer -mmmx -msse -mfpmath=sse"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp://linux.ntcu.net/dists/gentoo/
http://ftp.isu.edu.tw/pub/Linux/Gentoo ftp://ftp.isu.edu.tw/pub/Linux/Gentoo
ftp://linux.thai.net/pub/mirrors/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.asia.gentoo.org/gentoo-portage"
USE="X alsa apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gnome
gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mozilla
moznocompose moznoirc moznomail mpeg ncurses nls oggvorbis opengl oss pam pcmcia
pda pdflib perl png pnp python qt quicktime readline sdl slang spell ssl svga
tcpd truetype usb wavelan wifi x86 xml2 xv xvid zlib"
Comment 1 Masatomo Nakano (RETIRED) gentoo-dev 2004-06-20 07:02:20 UTC
Your timestamp.chk files looks broken.
I'll add an exception code for this problem to portage.

You can fix these command as well.
1. rm /usr/portage/metadata/timestamp.chk /var/tmp/timestamp.chk
2. emerge sync

Before doing the commands, can you post the files here for me?
Comment 2 Callan Tham 2004-06-20 07:43:50 UTC
Created attachment 33638 [details]
/usr/portage/metadata/timestamp.chk

As requested, I have attached the /usr/portage/metadata/timestamp.chk file.
However, I cannot find /var/tmp/timestamp.chk on my system at all. Could this
be the problem?
Comment 3 Masatomo Nakano (RETIRED) gentoo-dev 2004-06-20 08:02:53 UTC
Sorry, it's /var/cache/edb/dep/timestamp.chk.

But the reason is that your /usr/portage/metadata/timestamp.chk is completely broken... It looks glsa file.

I don't understand why it happens.
Maybe, your hard disk problem..

Anyway, you can delete the file and emerge sync again.
Then, if the problem happens again let me know.

(I've just added exeption code for ignoring broken timestamp.chk to CVS.)
Comment 4 Callan Tham 2004-06-20 08:54:56 UTC
First of all, thank you for solving this problem. Won't know what to do if not for you!

I have removed /usr/portage/metadata/timestamp.chk and am able to emerge sync my portage tree now. I hope it's not a hard disk problem though.

I do remember halting portage syncs several times, pressing ^C to stop it abruptly. Hopefully that is not the cause, but could that possibly bork the timestamp.chk file?
Comment 5 Callan Tham 2004-06-21 06:16:33 UTC
Just to confirm emerge sync and other operations are working fine after I removed the /usr/portage/metadata/timestamp.chk file; I guess the bug can be closed?
Comment 6 Callan Tham 2004-07-27 18:41:49 UTC
As stated above, the fix suggested by Masatomo Nakano worked for me.