From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] System maintenance procedure?
Date: Sun, 9 Dec 2012 07:18:42 -0600 [thread overview]
Message-ID: <20121209131841.GX23914@server> (raw)
In-Reply-To: <50C3CB44.7070307@gmail.com>
On Sat, Dec 08, 2012 at 05:20:36PM -0600, Dale wrote:
>
> That's been my experience too. I run @preserved-rebuild when it tells
> me to but revdep-rebuild rarely finds anything. Thing is, it has a time
> or two. It is best to run revdep-rebuild and be sure than not to and
> run the risk of not being able to boot or some other problem that bites
> you.
>
> Sort of like a ounce of prevention is worth a pound of cure. ;-)
>
> Dale
Wasn't following this thread closely when it began...
What is @preserved-rebuild ?
workstation ~ # @preserved-rebuild -p
-bash: @preserved-rebuild: command not found
workstation ~ # e-file @preserved-rebuild
No matches found.
workstation ~ # e-file preserved-rebuild
No matches found.
workstation ~ # preserved-rebuild -p
-bash: preserved-rebuild: command not found
workstation ~ # emerge -a @preserved-rebuild
emerge: 'preserved-rebuild' is an empty set
emerge: no targets left after set expansion
workstation ~ # emerge -a preserved-rebuild
These are the packages that would be merged, in order:
Calculating dependencies... done!
emerge: there are no ebuilds to satisfy "preserved-rebuild".
emerge: searching for similar names...
emerge: Maybe you meant any of these: app-portage/smart-live-rebuild, app-admin/chef-server-webui?
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2012-12-09 13:20 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 0:30 [gentoo-user] System maintenance procedure? Grant
2012-12-05 1:00 ` nybblenybblebyte
2012-12-05 1:21 ` Dale
2012-12-05 3:55 ` Grant
2012-12-05 1:36 ` Neil Bothwick
2012-12-05 4:04 ` Grant
2012-12-05 4:34 ` Dale
2012-12-05 5:15 ` Grant
2012-12-05 10:22 ` Dale
2012-12-08 0:57 ` Grant
2012-12-08 22:04 ` Grant
2012-12-08 23:25 ` Dale
2012-12-15 3:38 ` Grant
2012-12-05 12:50 ` Neil Bothwick
2012-12-08 0:55 ` Grant
2012-12-05 3:15 ` Pandu Poluan
2012-12-05 3:29 ` Allan Gottlieb
2012-12-05 3:34 ` Dale
2012-12-05 10:05 ` Alan McKinnon
2012-12-08 0:56 ` Grant
2012-12-08 11:58 ` Neil Bothwick
2012-12-08 20:06 ` Alan McKinnon
2012-12-08 21:07 ` Grant
2012-12-08 21:25 ` Alan McKinnon
2012-12-08 21:54 ` Grant
2012-12-08 22:08 ` Alan McKinnon
2012-12-09 0:41 ` Grant
2012-12-08 22:49 ` Neil Bothwick
2012-12-08 23:20 ` Dale
2012-12-09 4:22 ` Dale
2012-12-09 13:18 ` Bruce Hill [this message]
2012-12-09 16:48 ` Neil Bothwick
2012-12-09 17:01 ` Bruce Hill
2012-12-09 19:06 ` Neil Bothwick
2012-12-11 13:36 ` Bruce Hill
2012-12-11 14:04 ` Neil Bothwick
2012-12-11 17:20 ` Michael Orlitzky
2012-12-12 6:05 ` Alan McKinnon
2012-12-12 9:29 ` Neil Bothwick
2012-12-12 15:10 ` Bruce Hill
2012-12-12 9:49 ` Neil Bothwick
2012-12-12 12:16 ` design [depois das dez]
2012-12-09 0:33 ` Peter Humphrey
2012-12-10 7:50 ` Daniel Wagener
2012-12-10 8:41 ` [gentoo-user] " Steven J. Long
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=20121209131841.GX23914@server \
--to=daddy@happypenguincomputers.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