[gentoo-dev] Serious portage problem...

* [gentoo-dev] Serious portage problem...
@ 2002-06-24 19:47 Burton Samograd
  2002-06-24 20:16 ` Christophe Vanfleteren
  2002-06-24 21:15 ` Ryan Phillips
  0 siblings, 2 replies; 6+ messages in thread
From: Burton Samograd @ 2002-06-24 19:47 UTC (permalink / raw
  To: gentoo-dev

I seem to be having some wierd problems with portage.  Here is an
example when I try to re-emerge portage:

----------------------------------------------------------

root@kruhft:/var/db/pkg/dev-libs# emerge portage
Calculating dependencies ...done!
>>> emerge sys-apps/portage-2.0.5 to /
>>> Unpacking source...
>>> Source unpacked.
gcc -O2 -march=i486 -pipe    sandbox.c   -o sandbox
gcc -O2 -march=i486 -pipe   -c -o libsandbox.o libsandbox.c
gcc -O2 -march=i486 -pipe  libsandbox.o -o libsandbox.so -ldl --shared

>>> Install portage-2.0.5 into /var/tmp/portage/portage-2.0.5/image/
    category sys-apps
running install
running build
running build_ext
building 'missingos' extension
creating build
creating build/temp.linux-i686-2.2
gcc -DNDEBUG -march=i686 -mcpu=i686 -O3 -pipe -fforce-addr
    -frerun-cse-after-loop -frerun-loop-opt -malign-functions=4
    -funroll-loops -fomit-frame-pointer -fexpensive-optimizations
    -fPIC -I/usr/include/python2.2 -c missingos.c -o
    build/temp.linux-i686-2.2/missingos.o -march=i686 -mcpu=i686 -O3
    -pipe -fforce-addr -frerun-cse-after-loop -frerun-loop-opt
    -malign-functions=4 -funroll-loops -fomit-frame-pointer
    -fexpensive-optimizations
creating build/lib.linux-i686-2.2
gcc -shared build/temp.linux-i686-2.2/missingos.o -o
    build/lib.linux-i686-2.2/missingos.so
running install_lib
creating /var/tmp/portage/portage-2.0.5/image/usr
creating /var/tmp/portage/portage-2.0.5/image/usr/lib
creating /var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2
creating
    /var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2/site-packages
copying build/lib.linux-i686-2.2/missingos.so ->
    /var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2/site-packages
warning: install: modules installed to
    '/var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2/site-packages/',
    which is not in Python's module search path (sys.path) -- you'll
    have to change the search path yourself
strip:
/var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2/site-packages/missingos.so/var/tmp/portage/portage-2.0.5/image/usr/lib/portage/bin/tbz2tool
/var/tmp/portage/portage-2.0.5/image/usr/lib/portage/bin/sandbox
/var/tmp/portage/portage-2.0.5/image/lib/libsandbox.so
>>> Completed installing into /var/tmp/portage/portage-2.0.5/image/

>>> Merging sys-apps/portage-2.0.5 to /
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1233, in ?
    mydepgraph.merge(mydepgraph.altlist())
  File "/usr/bin/emerge", line 610, in merge
    retval=portage.doebuild(y,"merge",myroot,edebug)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1212, in
  doebuild
    return
    merge(settings["CATEGORY"],settings["PF"],settings["D"],settings["BUILDDIR"]+"/build-info",myroot,myebuild=settings["EBUILD"])
  File "/usr/lib/python2.2/site-packages/portage.py", line 1436, in
  merge
    mylink.merge(pkgloc,infloc,myroot,myebuild)
  File "/usr/lib/python2.2/site-packages/portage.py", line 3340, in
  merge
    self.treewalk(mergeroot,myroot,inforoot,myebuild)
  File "/usr/lib/python2.2/site-packages/portage.py", line 3016, in
  treewalk
    packagecounter=long(globalcounterfile.readline())
ValueError: invalid literal for long(): 

---------------------------------------------------------

Basically emerge has become useless.  Anybody have this problem
before, or is there a way to reinstall just portage from a package if
it's screwed up like this?

^ permalink raw reply	[flat|nested] 6+ messages in thread