From: Ryan Shaw <ryan.shaw@stanfordalumni.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] running ebuild on an ebuild not in the portage tree?
Date: 25 Jun 2002 22:25:51 +0900 [thread overview]
Message-ID: <1025011577.4982.4.camel@momo> (raw)
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
hello,
i usually develop ebuilds by working on them
in my home directory, and using the "ebuild"
command (rather than "emerge") to try out the
different stages before submitting.
this used to (2 weeks ago) work just fine:
ebuild ant-1.5_beta3.ebuild digest
but now i get:
!!! doebuild: /usr/portage/dev-java/ant/ant-1.5_beta3.ebuild not found.
Traceback (most recent call last):
File "/usr/sbin/ebuild", line 33, in ?
a=portage.doebuild(pargs[0],x,getroot(),debug=debug)
File "/usr/lib/python2.2/site-packages/portage.py", line 1073, in
doebuild
settings["SLOT"], settings["RESTRICT"], myuris =
db["/"]["porttree"].dbapi.aux_get(mykey,["SLOT","RESTRICT","SRC_URI"])
File "/usr/lib/python2.2/site-packages/portage.py", line 2548, in
aux_get
mycent=open(mydbkey,"r")
IOError: [Errno 2] No such file or directory:
'/var/cache/edb/dep/dev-java/ant-1.5_beta3'
what happened?
ryan
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2002-06-25 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1025011577.4982.4.camel@momo \
--to=ryan.shaw@stanfordalumni.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