From: "David Pyke" <dpyke@researchdimensions.com>
To: <gentoo-amd64@lists.gentoo.org>
Subject: RE: [gentoo-amd64] Install snapshot update?
Date: Tue, 9 Jan 2007 10:18:20 -0500 [thread overview]
Message-ID: <003501c73401$65d184f0$6f0a0a0a@RDLaptop3> (raw)
In-Reply-To: <4d192b620701090711x2761082ds267cee2532f6d15d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Yes but I don't think the GTK installer does. Or, if it does, it doesn't use the updated snapshot for emerging the packages.
For my own install, I ended up doing mostly a manual install once the kernel was installed. I did a --sync and then started the install of xorg and gnome. It's now running an emerge -uDN to get everything up to snuff.
_____
From: Javi Moreno [mailto:vierito5@gmail.com]
Sent: Tuesday, January 09, 2007 10:12 AM
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Install snapshot update?
On 1/9/07, David Pyke <dpyke@researchdimensions.com> wrote:
I just went through the install process for amd64 on my Acer 5050 laptop (turion) and ran into a few problems with the install, mostly with out of date packages (xterm-215 is no longer available). It took 4 attempts to get to the install portion where I could reboot and resume the build after the emerge failed.
Is there some way to have the installer run emerge --sync before it starts building the system?
Actually, before compiling you have to emerge --sync, after the chroot.
--
David Pyke
Vice President, Research
Research Dimensions
416-486-6161
800-663-2973
--
gentoo-amd64@gentoo.org mailing list
[-- Attachment #2: Type: text/html, Size: 2574 bytes --]
prev parent reply other threads:[~2007-01-09 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 14:09 [gentoo-amd64] Install snapshot update? David Pyke
2007-01-09 15:11 ` Javi Moreno
2007-01-09 15:18 ` David Pyke [this message]
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='003501c73401$65d184f0$6f0a0a0a@RDLaptop3' \
--to=dpyke@researchdimensions.com \
--cc=gentoo-amd64@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