From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Any vbox made gentoo vm appliances available for dload
Date: Sun, 27 Nov 2011 04:52:31 -0600 [thread overview]
Message-ID: <87fwh9alcg.fsf@newsguy.com> (raw)
In-Reply-To: 1322358252.8604.3.camel@stretch
"Albert W. Hopkins" <marduk@letterboxes.org> writes:
> On Sat, 2011-11-26 at 17:01 -0600, Harry Putnam wrote:
>> Creating a gentoo vm has always been a serious pita to me. I'm sure
>> there will be those who claim its `simple'.
>>
>> Simple or not, I want to bypass it if possible.
>>
>> So wondering if anyone here has (or has seen) a gentoo (vbox)
>> appliance available for download?
>>
>>
> I maintain a quasi-daily build of a gentoo virtual appliance. It should
> work with kvm, vmware, and virutalbox (and possibly xen?).
Albert, I cloned your hg repo and tried to build from it, but it fails
at downloading gentoo-sources. Something about not being able to
resolve the kernel URLS.
I suspect it is a problem in the ebuild itself, but I was not able to
find where `portage' is on disc during that build. I wanted to
attempt editing the ebuild but even with variable:
REMOVE_PORTAGE_TREE NO
I never find a `portage' directory.
Once the build fails, their is no `portage' directory containing the
tree.
In virtual-appliance:
find . -type d -name 'portage'
./vabuild/var/lib/portage
./vabuild/var/log/portage
./vabuild/var/cache/edb/dep/usr/portage
./vabuild/usr/lib/portage
./vabuild/usr/lib/portage/pym/portage
None of those contain the tree.
Here is tail of `sudo make'
,----
| Resolving www.fr.kernel.org... failed: Name or service not known.
| wget: unable to resolve host address “www.fr.kernel.org”
| >>> Downloading 'http://www.us.kernel.org/pub/linux/kernel/v3.x/linux-3.1.tar.bz2'
| --2011-11-27 04:24:43-- http://www.us.kernel.org/pub/linux/kernel/v3.x/linux-3.1.tar.bz2
| Resolving www.us.kernel.org... failed: Name or service not known.
| wget: unable to resolve host address “www.us.kernel.org”
| !!! Couldn't download 'linux-3.1.tar.bz2'. Aborting.
| * Fetch failed for 'sys-kernel/gentoo-sources-3.1.1', Log file:
| * '/var/tmp/portage/sys-kernel/gentoo-sources-3.1.1/temp/build.log'
|
| * Messages for package sys-kernel/gentoo-sources-3.1.1:
|
| * Fetch failed for 'sys-kernel/gentoo-sources-3.1.1', Log file:
| * '/var/tmp/portage/sys-kernel/gentoo-sources-3.1.1/temp/build.log'
`----
I cannot ping any of those kernel urls. But kernel.org appears up
ping kernel.org
PING kernel.org (149.20.4.69) 56(84) bytes of data.
64 bytes from pub2.kernel.org (149.20.4.69): icmp_req=1 ttl=55 time=87.5 ms
ls vabuild/var/tmp/
<empty>
Apparently umounted or rm'd
How to keep working portage tree accessible.
I monkeyed around with your Makefile but couldn't follow it well
enough to stop the umounting.
next prev parent reply other threads:[~2011-11-27 10:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 23:01 [gentoo-user] Any vbox made gentoo vm appliances available for dload Harry Putnam
2011-11-26 23:21 ` Mark Knecht
2011-11-27 1:27 ` James Wall
2011-11-27 10:53 ` [gentoo-user] " Harry Putnam
2011-11-27 1:44 ` [gentoo-user] " Albert W. Hopkins
2011-11-27 3:18 ` Vishnupradeep
2011-11-27 12:10 ` Albert W. Hopkins
2011-11-27 3:23 ` Vishnupradeep
2011-11-27 12:10 ` Albert W. Hopkins
2011-11-27 10:52 ` Harry Putnam [this message]
2011-11-27 12:28 ` [gentoo-user] " Albert W. Hopkins
2011-11-27 19:38 ` Harry Putnam
2011-11-27 10:59 ` Harry Putnam
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=87fwh9alcg.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@lists.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