public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "mike" <vapier@netzero.com>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Is my portage broken?
Date: Wed, 18 Sep 2002 08:44:57 -0400	[thread overview]
Message-ID: <015501c25f11$31bc4520$55f1d782@vapier> (raw)
In-Reply-To: 20020918074332.GA5471@lion.e-technik.uni-ulm.de

you could `rm -rf /usr/portage/*` and not worry
about messing up your system.  it'll just take a lot
longer to complete `emerge rsync`.
that might be a good idea if you're running an old
version of portage and/or have old ebuilds.
`emerge rsync ; emerge portage -u ; emerge world -up`
-mike

----- Original Message ----- 
From: "Serge Eric Thiam" <serge-eric.thiam@gmx.net>
To: <gentoo-dev@gentoo.org>
Sent: Wednesday, September 18, 2002 03:43
Subject: Re: [gentoo-dev] Is my portage broken?


> * Thomas Rasch [Tue, Sep 17, 2002 at 08:20:22PM +0200]
> > Hello!
> > 
> > I didn't get an answer to this question in the gentoo-user mailinglist,
> > so it seems to be more tricky than I thought... 
> > 
> > To make it short: I made an emerge rsync, and something didn't
> > survive...
> > 
> > emerge -up world gives:
> > 
> > Calculating world dependencies  
> > Traceback (most recent call last):
> >   File "/usr/bin/emerge", line 1369, in ?
> >     if not mydepgraph.xcreate(myaction):
> >   File "/usr/bin/emerge", line 805, in xcreate
> >     elif portage.db[portage.root]["vartree"].dbapi.match(x):
> >   File "/usr/lib/python2.2/site-packages/portage.py", line 2522, in
> > match
> >     mydep=dep_expand(origdep,self)
> >   File "/usr/lib/python2.2/site-packages/portage.py", line 2037, in
> > dep_expand
> >     return prefix+cpv_expand(mydep,mydb)+postfix
> >   File "/usr/lib/python2.2/site-packages/portage.py", line 1970, in
> > cpv_expand
> >     if (not mydb.cp_list(mykey)) and virts and virts.has_key(mykey):
> >   File "/usr/lib/python2.2/site-packages/portage.py", line 2481, in
> > cp_list
> >     mystat=os.stat(self.root+"var/db/pkg/"+mysplit[0])[ST_MTIME]
> > TypeError: stat() argument 1 must be (encoded string without NULL
> > bytes), not str
> > [...]
> > 
> > Thomas
> > [...]
> 
> Hello, 
> 
> There might be a broken ebuild in your portage tree. Try to clean up
> your portage tree, (maby deleting all the ebuilds) before doing an
> emerge rsync and try again. It would be a good idea to backup first, you
> never know what might happen.... don't want to cause harm to your
> system.
> 
> Good luck,
> --
> Serge
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> 



  reply	other threads:[~2002-09-18 12:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17 18:20 [gentoo-dev] Is my portage broken? Thomas Rasch
2002-09-18  7:43 ` Serge Eric Thiam
2002-09-18 12:44   ` mike [this message]
2002-09-18 16:14     ` Thomas Rasch
2002-09-18 17:51       ` mike

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='015501c25f11$31bc4520$55f1d782@vapier' \
    --to=vapier@netzero.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox