From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Power failure in the middle of emerge --emptytree world
Date: Mon, 24 Jul 2006 19:26:13 -0700 [thread overview]
Message-ID: <5bdc1c8b0607241926o57557e00uddffac0a644fc0d0@mail.gmail.com> (raw)
Hi,
A hot summer day blew the power transformer in my backyard. One of
my MythTV frontends was about 2/3 of the way through an emerge
--emptytree world at the time:
1153780822: === (178 of 280) Post-Build Cleaning
(x11-proto/scrnsaverproto-1.1.0::/usr/portage/x11-proto/scrnsaverproto/scrnsaverproto-1.1.0.ebuild)
1153780822: ::: completed emerge (178 of 280)
x11-proto/scrnsaverproto-1.1.0 to /
1153780822: >>> emerge (179 of 280) x11-base/xorg-server-1.0.2-r7 to /
1153780822: === (179 of 280) Cleaning
(x11-base/xorg-server-1.0.2-r7::/usr/portage/x11-base/xorg-server/xorg-server-1.0.2-r7.ebuild)
1153780822: === (179 of 280) Compiling/Merging
(x11-base/xorg-server-1.0.2-r7::/usr/portage/x11-base/xorg-server/xorg-server-1.0.2-r7.ebuild)
1153781845: *** terminating.
What is my best course of action at this point? The machine booted
fine so I could start over. I also saved an old email from Zac Medico
that suggested a command
FEATURES=keepwork emerge --resume
Would this be a good thing to do?
There are currently 5 files to be dealt with under etc-update.
Should I do those first?
Thanks,
Mark
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-07-25 2:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 2:26 Mark Knecht [this message]
2006-07-25 2:46 ` [gentoo-user] Power failure in the middle of emerge --emptytree world Dale
2006-07-25 4:02 ` Zac Medico
2006-07-25 14:45 ` Mark Knecht
2006-07-25 18:39 ` Dale
2006-07-25 19:58 ` Mark Knecht
2006-07-25 20:29 ` Dale
2006-07-25 22:10 ` Zac Medico
2006-07-26 1:04 ` Dale
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=5bdc1c8b0607241926o57557e00uddffac0a644fc0d0@mail.gmail.com \
--to=markknecht@gmail.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