From: Mark <whitetr6@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] backups and world updates
Date: Thu, 28 Jul 2005 11:13:18 -0400 [thread overview]
Message-ID: <1f81f7e005072808137d93cae8@mail.gmail.com> (raw)
In-Reply-To: <42E8EA25.2030302@cisco.com>
Hi Roy, I wasn't able to find it. Can you post your version? This
sounds like the approach I'd like to take. Thanks!
On 7/28/05, Roy Wright <royw@cisco.com> wrote:
> Howdy,
>
> What I do is run a nightly script that:
> * cleans up tmp files
> * runs revdep-rebuild
> * runs emerge --sync
> * runs eupdatedb
> * runs update-eix
> * runs a pretend emerge -uDNvp world
> * runs a fetchonly emerge -uDNq --fetchonly world
> * greps the ebuilds for einfo, ewarn, and eerror lines
> * runs glsa-check
> The output of everything is then mailed to me.
> I originally got the script from the gentoo-users list
> but didn't save the link (maybe scan the archives for
> portage.cron or if you want I can post what I have).
>
> Then I review the email and decide when to update.
>
> A red flag is if the einfo mentions revdep-rebuild.
> In that case I emerge that package by name allowing
> dependencies, then do the revdep-rebuild, then
> the emerge world.
>
> Most of the time, I just open an konsole and do the
> update. Occasionally I'll postpone if the update looks
> really large or time consuming. For major gui components
> like KDE or xorg, I'll exit KDE and emerge from the
> command line over the weekend (ok, probably overly
> cautious, but I was burned once).
>
> Occasionally I'll get a blocking condition. I really think
> twice now before just unblocking via package.keywords.
> I've found that waiting a day or two might result in
> portage handling the unblocking.
>
> HTH,
> Roy
>
> Mark wrote:
>
> >Thanks to everyone who helped me get my system back after a couple of
> >world update snafus. Now of course I'm a little gun-shy about using
> >options like emerge --update world. So what's my best bet to keep my
> >system up to date, while protecting it from my own lack of
> >understanding of updating config files?
> >
> >Here's what I'm intending to do so far:
> >
> >1. Prior to running any large system update, back up /etc to another location
> >2. use dispatch-conf instead of etc-update
> >
> >Can anyone make any other suggestions? Which emerge options are best
> >for full system updates? Thanks
> >
> >
> --
> gentoo-amd64@gentoo.org mailing list
>
>
--
Mark
[unwieldy legal disclaimer would go here - feel free to type your own]
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-28 15:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 13:53 [gentoo-amd64] backups and world updates Mark
2005-07-28 14:11 ` Brett Johnson
2005-07-31 3:48 ` [gentoo-amd64] emerge of neverwinter nights fails Mark Creamer
2005-07-31 3:57 ` shimi
2005-07-31 9:24 ` Michal Žeravík
2005-07-31 9:51 ` Peter Humphrey
2005-07-31 17:05 ` phil
2005-07-31 21:39 ` Michal Žeravík
2005-07-31 23:05 ` Mark Creamer
2005-08-01 15:59 ` Chuck Milam
2005-08-01 16:11 ` Peter Humphrey
2005-08-01 17:10 ` Chuck Milam
2005-08-01 20:10 ` phil
2005-08-01 18:49 ` phil
2005-07-31 9:25 ` [gentoo-amd64] " Duncan
2005-07-28 14:22 ` [gentoo-amd64] backups and world updates Roy Wright
2005-07-28 15:13 ` Mark [this message]
2005-07-28 18:32 ` Roy Wright
2005-07-28 15:47 ` Matt Randolph
2005-07-28 15:15 ` Matt Randolph
2005-07-29 14:25 ` [gentoo-amd64] " Duncan
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=1f81f7e005072808137d93cae8@mail.gmail.com \
--to=whitetr6@gmail.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