From: Thomas Preissler <tomjohn@gmx.de>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Creating digest for new subtree fails
Date: Sun, 8 Dec 2002 14:34:21 +0100 [thread overview]
Message-ID: <20021208133421.GA13705@zeus.tpfm.de> (raw)
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
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...
I think, that "opera-shared" is not known as a valid "sub-tree".
My question is, how can I add new "subtrees" under the main tree
like "net-www"? It is important, that I use /usr/local/portage/ and
not /usr/portage/ one. Creating digests of other ebuild's works
fine, like fvwm-2.4.14.
Greetz,
Tom
--
Preissler Thomas Registered Linux User #265745
GPG-Key: 1024D/C21DAB7F http://counter.li.org/
printk("Illegal format on cdrom. Pester manufacturer.\n");
2.2.16 /usr/src/linux/fs/isofs/inode.c
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2002-12-08 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 13:34 Thomas Preissler [this message]
2002-12-08 18:20 ` [gentoo-dev] SOLVED (was: Re: [gentoo-dev] Creating digest for new subtree fails) Thomas Preissler
2002-12-09 8:26 ` [gentoo-dev] Creating digest for new subtree fails 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=20021208133421.GA13705@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