From: Thomas Preissler <tomjohn@gmx.de>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] SOLVED (was: Re: [gentoo-dev] Creating digest for new subtree fails)
Date: Sun, 8 Dec 2002 19:20:53 +0100 [thread overview]
Message-ID: <20021208182053.GA15541@zeus.tpfm.de> (raw)
In-Reply-To: <20021208133421.GA13705@zeus.tpfm.de>
* Thomas Preissler wrote on 08 Dec 2002:
> Hello,
>
> I just made an opera-shared-6.11 ebuild. The problem is, that
> portage/net-www/opera-shared does not exist, so I created it and put
> my ebuild there.
>
> Creating the digest fails with this message:
>
> host /usr/local/portage/net-www/opera-shared $ emerge net-www/opera-shared-6.11.ebuild digest
My fault. It must be "ebuild", and not "emerge".
> Calculating dependencies \!!! Failed to stat ebuild:
> /usr/portage/opera-shared/opera-shared/opera-shared-6.11.ebuild
> !!! doebuild: /usr/portage/opera-shared/opera-shared/opera-shared-6.11.ebuild not found.
> portage: aux_get(): (1) couldn't open cache entry for opera-shared/opera-shared-6.11
> (likely caused by syntax error or corruption in the opera-shared/opera-shared-6.11 ebuild.)
> emerge: create(): aux_get() error on opera-shared/opera-shared-6.11; aborting...
[...]
Greetz,
Tom
--
Preissler Thomas Registered Linux User #265745
GPG-Key: 1024D/C21DAB7F http://counter.li.org/
For every problem, there exists a simple and elegant solution that is
absolutely wrong.
-- J. Wagoner
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2002-12-08 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 13:34 [gentoo-dev] Creating digest for new subtree fails Thomas Preissler
2002-12-08 18:20 ` Thomas Preissler [this message]
2002-12-09 8:26 ` Martin Cooper
2002-12-09 13:42 ` Thomas Preissler
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=20021208182053.GA15541@zeus.tpfm.de \
--to=tomjohn@gmx.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