Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
bootstrap.sh seriously b0rked (PORTAGE_TMPDIR invalid)
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
Scytale
n00b
n00b


Joined: 01 May 2003
Posts: 70
Location: Mannheim, BW, Germany

PostPosted: Mon Mar 01, 2004 5:13 pm    Post subject: bootstrap.sh seriously b0rked (PORTAGE_TMPDIR invalid) Reply with quote

Hi folks!

First of all, I'm no Gentoo Newbie. I'm installing this wonderful distribution on everything that doesn't run away fast enough (and happily computers aren't that good runners), but I guess this time it's been one time too much.

I am installing on this Duron 800 box over SSH, stage1, 1.4 LiveCD. I'm using DistCC, so this installation is supported by a Athlon XP 2400+. Now, the mistake I made was to go shopping during bootstrap. When I came home I had to find out that the WLAN connection of my notebook (that one with the SSH client controlling the installation) died. So what happened was, the bootstrap process lost its terminal and died.

Okay, shouldn't be that bad, just chroot again, env-update, source profile and voila... that's the error message:
Code:
cdimage portage # scripts/bootstrap.sh

Gentoo Linux; http://www.gentoo.org/
Copyright 2001-2003 Gentoo Technologies, Inc.; Distributed under the GPL
Starting Bootstrap of base system ...

Invalid or unset record 'packages' in mtimedb.
Invalid or unset record 'eclass' in mtimedb.
Using >=sys-apps/baselayout-1.7.9-r1
Using >=sys-apps/portage-2.0.25
Using >=sys-devel/binutils-2.13.90.0.4
Using >=sys-devel/gcc-3.2
Using sys-devel/gettext
Using >=sys-libs/glibc-2.2.5
Using >=sys-apps/texinfo-4.2-r1
Using sys-libs/zlib
Using >=sys-libs/ncurses-5.2.20020112a

Configuring environment...

!!! INVALID ACCEPT_KEYWORD: x86

!!! INVALID ACCEPT_KEYWORD: x86

!!! INVALID ACCEPT_KEYWORD: x86
portage: the directory specified in your PORTAGE_TMPDIR variable, "!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
/var/tmp,"
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.
portage: the directory specified in your PORTAGE_TMPDIR variable, "!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
/var/tmp,"
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.
portage: the directory specified in your PORTAGE_TMPDIR variable, "!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
/var/tmp,"
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.
portage: the directory specified in your PORTAGE_TMPDIR variable, "!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
/var/tmp,"
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.
portage: the directory specified in your PORTAGE_TMPDIR variable, "!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
/var/tmp,"
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.
portage: the directory specified in your PORTAGE_TMPDIR variable, "!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
/var/tmp,"
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.
exporting PROXY=!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
portage: the directory specified in your PORTAGE_TMPDIR variable, "!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
/var/tmp,"
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.
exporting HTTP_PROXY=!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
portage: the directory specified in your PORTAGE_TMPDIR variable, "!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
/var/tmp,"
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.
exporting FTP_PROXY=!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
portage: the directory specified in your PORTAGE_TMPDIR variable, "!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9.portage_lockfile
!!! Invalid db entry: /var/db/pkg/sys-libs/-MERGING-glibc-2.3.2-r9
/var/tmp,"
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.


This is just evil. I have no clue how to fix this and don't want to start all over again. Is there a simple solution to that problem?
_________________
Never stop using your brain.
Back to top
View user's profile Send private message
KaZeR
Apprentice
Apprentice


Joined: 04 Feb 2004
Posts: 291
Location: Au fond, à droite.

PostPosted: Mon Mar 01, 2004 5:18 pm    Post subject: Reply with quote

Did you correctly remount all your target partitions?
Is there space left in /var/tmp?
You could try changing tmpdir with
Code:
export PORTAGE_TMPDIR="/wherever/you/want"


Hope this will help..

Goodluck :)
_________________
Foo.
Back to top
View user's profile Send private message
Scytale
n00b
n00b


Joined: 01 May 2003
Posts: 70
Location: Mannheim, BW, Germany

PostPosted: Mon Mar 01, 2004 5:23 pm    Post subject: Reply with quote

KaZeR wrote:
Did you correctly remount all your target partitions?

No need, the target box did not reboot.

KaZeR wrote:
Is there space left in /var/tmp?

About 9.6 Gigs.

KaZeR wrote:
You could try changing tmpdir with
Code:
export PORTAGE_TMPDIR="/wherever/you/want"

Doesn't work, same error message. Looks like the variable gets overwritten somewhere in bootstrap.sh.
_________________
Never stop using your brain.
Back to top
View user's profile Send private message
Scytale
n00b
n00b


Joined: 01 May 2003
Posts: 70
Location: Mannheim, BW, Germany

PostPosted: Mon Mar 01, 2004 5:47 pm    Post subject: Reply with quote

Okay, after
Code:
rm -rf -- /var/db/pkg/sys-libs/-MERGING-*
I can start bootstrapping again, although the "Invalid or unset record" messages at the beginning still appear. I'll play around a bit and try to get rid of them.
_________________
Never stop using your brain.
Back to top
View user's profile Send private message
Ronald Dehuysser
n00b
n00b


Joined: 18 Nov 2003
Posts: 26

PostPosted: Mon May 03, 2004 3:25 pm    Post subject: Did you solve your problem? Reply with quote

Did you find a solution for your problem? When trying to bootstrap I receive this error:

Code:
ronald01 portage # scripts/bootstrap.sh

Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2004 Gentoo Technologies, Inc.; Distributed under the GPL
Starting Bootstrap of base system ...

Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Using >=sys-apps/baselayout-1.7.9-r1
Using >=sys-apps/portage-2.0.25
Using >=sys-devel/binutils-2.13.90.0.4
Using >=sys-devel/gcc-3.2
Using sys-devel/gettext
Using >=sys-libs/glibc-2.2.5
Using >=sys-apps/texinfo-4.2-r1
Using sys-libs/zlib
Using >=sys-libs/ncurses-5.2.20020112a

Configuring environment...
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "portage.py", line 21, in ?
    import missingos
ImportError: No module named missingos
portage: the directory specified in your PORTAGE_TMPDIR variable, ","
does not exist.  Please create this directory or correct your PORTAGE_TMPDIR setting.



Already tried to export PORTAGE_TMPDIR to another directory... no use. I also set in make.conf but no result.

Anybody has an idea ?

Thanks in advance,
Ronald
Back to top
View user's profile Send private message
Ronald Dehuysser
n00b
n00b


Joined: 18 Nov 2003
Posts: 26

PostPosted: Tue May 04, 2004 8:36 am    Post subject: Still no success... Reply with quote

I must be doing something wrong since I am the only one having this problem. I reread the complete handbook and even tried the 2004.0 stages with no luck...

Can anybody tell me what I forgot?

These are the last steps of what I did with a minimal 2004.1 Livecd...
- chrooting works fine, I did all the mounts described in the handbook
- then I changed my /etc/make.conf and used the following:
CFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe"
(I don't think these are to aggresive, I used them till now with the 1.4 release)
Since the default mirror didn't respond, I added this entry
SYNC="rsync://rsync1.no.gentoo.org/gentoo-portage"
- emerge synced
- cd /usr/portage
- scripts/bootstrap.sh

then I have the above error...

Am I overseeing something? Please tell me...
Back to top
View user's profile Send private message
t_2199
Tux's lil' helper
Tux's lil' helper


Joined: 20 Mar 2004
Posts: 146

PostPosted: Tue May 04, 2004 9:54 am    Post subject: Re: Still no success... Reply with quote

Ronald Dehuysser wrote:
I must be doing something wrong since I am the only one having this problem. I reread the complete handbook and even tried the 2004.0 stages with no luck...

Can anybody tell me what I forgot?

These are the last steps of what I did with a minimal 2004.1 Livecd...
- chrooting works fine, I did all the mounts described in the handbook
- then I changed my /etc/make.conf and used the following:
CFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe"
(I don't think these are to aggresive, I used them till now with the 1.4 release)
Since the default mirror didn't respond, I added this entry
SYNC="rsync://rsync1.no.gentoo.org/gentoo-portage"
- emerge synced
- cd /usr/portage
- scripts/bootstrap.sh

then I have the above error...


I would try to start from the beginning again! Delete your whole partition and start again.. (shouldnt take that long anyway)
Am I overseeing something? Please tell me...
Back to top
View user's profile Send private message
Ronald Dehuysser
n00b
n00b


Joined: 18 Nov 2003
Posts: 26

PostPosted: Tue May 04, 2004 3:36 pm    Post subject: Solved it!! Reply with quote

Hi guys, I solved it ...

I reformatted the partition plenty times before ... that didn't work out either.

But there could be two reasons:
Now I downloaded the universal livecd instead of the minimal and used the stage1 provided on this cd.
I also used mirrorselect this time instead of copying my old SYNC value.

But how come this solved it... isn't this a bug?

Bootstrapping as we speak :)

Cheers,
Ronald
Back to top
View user's profile Send private message
marcic
n00b
n00b


Joined: 31 Dec 2003
Posts: 3

PostPosted: Sun Jun 06, 2004 4:16 pm    Post subject: Reply with quote

having the same problem here... haven't tried to reformat and start everything from the beginning but probably will have to. haven't seen that kind of error before.

marcic
Back to top
View user's profile Send private message
Ronald Dehuysser
n00b
n00b


Joined: 18 Nov 2003
Posts: 26

PostPosted: Sun Oct 03, 2004 9:16 pm    Post subject: solved it Reply with quote

The issue was solved using the stage provided on the universal cd, thus also the packages which where out-of-date.

Reformatting didn't solve the issue either. Finnaly, I tried looking it up on bugzilla and found the answer over there. In /usr/portage/portage.py comment out the two lines with the word missingos and bootstrap will continue as normal.

What are these two lines for? Why aren't they removed from portage system? Is it an issue for our bughunting day?

Regards,
Ronald
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum