From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] eclass GPL-2 error
Date: 04 Jul 2003 22:02:34 -0400 [thread overview]
Message-ID: <1057370554.3232.7.camel@localhost> (raw)
In-Reply-To: <auto-000079927628@remt30.cluster1.charter.net>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
On Fri, 2003-07-04 at 21:51, Brett I. Holcomb wrote:
> I and others have been getting this error after an emerge sync. It happens
> on various mirrors.
>
> > >>> Updating Portage cache... \!!! eclass 'GPL-2' in 'GPL-2' does not exist:
>
> What is this and what can I do about it. At this point I have several apps
> that need update but emerge -u --deep world (or system) -p don't show they
> need updating. I tried to check the bug that was file but bugzilla is still
> down.
It's a known problem, but w/o a known solution atm, I'm afraid.
--
Grant Goodyear <g2boojum@gentoo.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-05 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 1:51 [gentoo-dev] eclass GPL-2 error Brett I. Holcomb
2003-07-05 2:02 ` Grant Goodyear [this message]
2003-07-05 2:07 ` Robin H.Johnson
2003-07-05 2:29 ` Grant Goodyear
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=1057370554.3232.7.camel@localhost \
--to=g2boojum@gentoo.org \
--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