From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] portage 1.5_pre5
Date: Thu Feb 22 00:59:01 2001 [thread overview]
Message-ID: <3A94C0BB.169343DD@gottinger.de> (raw)
In-Reply-To: 20010221102942.B8459@cvs.gentoo.org
drobbins@gentoo.org wrote:
>
> Hi All,
>
> I just committed portage 1.5_pre5, which now performs numerous consistency
> checks on cat/pkg strings. Portage should now gracefully handle invalid
> current-packages lines, invalid /var/db/pkg entries, invalid /usr/portage
> entries, and invalid .tbz2 files. It will print Error messages to stdout
> and continue, so that the errors can be detected and eventually corrected.
>
> If your version of portage is dying because one of your databases
> (current-packages, /var/db/pkg, or /usr/portage) has an invalid entry, simply
> do this:
>
> 1. Do a cvs update.
> 2. Copy /usr/portage/sys-apps/portage/files/1.5/pym/portage.py to
> /usr/lib/python2.0/portage.py
>
> If you're not getting python errors, then a simple merge of the new version
> should suffice.
>
> Let me know if this solves the problem.
Great it works. Looks like creating dirs in virtual to fake installed
packages caused my errors.
thx achim~
>
> --
> Daniel Robbins <drobbins@gentoo.org>
> President/CEO http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2001-02-22 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 10:30 [gentoo-dev] portage 1.5_pre5 drobbins
2001-02-22 0:59 ` Achim Gottinger [this message]
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=3A94C0BB.169343DD@gottinger.de \
--to=320095285153-0001@t-online.de \
--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