From: Ferris McCormick <fmccor@inforead.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] More on portage 2.0.50
Date: Sat, 7 Feb 2004 02:16:27 +0000 (UTC) [thread overview]
Message-ID: <Pine.LNX.4.58.0402070211030.9908@terciopelo.krait.us> (raw)
In-Reply-To: <200402062116.01881.vapier@gentoo.org>
On Fri, 6 Feb 2004, Mike Frysinger wrote:
> On Friday 06 February 2004 08:44 pm, Ferris McCormick wrote:
> > When you force a corresponding upgrade to gentoolkit-0.2.0_pre5,
> > etcat becomes broken:
..................
..................
>
> > unlink: /usr/lib/portage/pym/portage_db_template.pyc
> > open_wr: /usr/lib/portage/pym/portage_db_template.pyc
> > unlink: /usr/lib/portage/pym/portage_db_flat.pyc
> > open_wr: /usr/lib/portage/pym/portage_db_flat.pyc
>
> did you look in bugzilla ? i remember seeing these things before and i kind
> of remember them being arch-specific, but i also remember them being
> fixed ...
> -mike
>
I don't know if it was architecture specific, but at one time it was
fixed. This was just reported as new by someone else on this mailing
list, too, (at about 00:00GMT), so I decided to pile on, because
it seems to be back with portage 2.0.50. I'll know in a while,
because I temporarily reverted to 2.0.49-r21, and am trying perl again.
But that takes a while.
--
Ferris McCormick (P44646, MI) <mccormickf@abanet.org>
Host: terciopelo (U2-SMP GenToo Linux)
Fax: (703) 392-0401
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-02-07 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 1:44 [gentoo-dev] More on portage 2.0.50 Ferris McCormick
2004-02-07 2:15 ` Mike Frysinger
2004-02-07 2:16 ` Ferris McCormick [this message]
2004-02-07 4:35 ` [gentoo-dev] More on portage 2.0.50 (4) Ferris McCormick
2004-02-07 9:56 ` Paul de Vrieze
2004-02-07 11:57 ` Ferris McCormick
2004-02-07 17:04 ` Alastair Tse
2004-02-07 17:53 ` Ferris McCormick
2004-02-07 18:03 ` Ferris McCormick
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=Pine.LNX.4.58.0402070211030.9908@terciopelo.krait.us \
--to=fmccor@inforead.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=vapier@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