| 1 |
Howdy, |
| 2 |
|
| 3 |
What I do is run a nightly script that: |
| 4 |
* cleans up tmp files |
| 5 |
* runs revdep-rebuild |
| 6 |
* runs emerge --sync |
| 7 |
* runs eupdatedb |
| 8 |
* runs update-eix |
| 9 |
* runs a pretend emerge -uDNvp world |
| 10 |
* runs a fetchonly emerge -uDNq --fetchonly world |
| 11 |
* greps the ebuilds for einfo, ewarn, and eerror lines |
| 12 |
* runs glsa-check |
| 13 |
The output of everything is then mailed to me. |
| 14 |
I originally got the script from the gentoo-users list |
| 15 |
but didn't save the link (maybe scan the archives for |
| 16 |
portage.cron or if you want I can post what I have). |
| 17 |
|
| 18 |
Then I review the email and decide when to update. |
| 19 |
|
| 20 |
A red flag is if the einfo mentions revdep-rebuild. |
| 21 |
In that case I emerge that package by name allowing |
| 22 |
dependencies, then do the revdep-rebuild, then |
| 23 |
the emerge world. |
| 24 |
|
| 25 |
Most of the time, I just open an konsole and do the |
| 26 |
update. Occasionally I'll postpone if the update looks |
| 27 |
really large or time consuming. For major gui components |
| 28 |
like KDE or xorg, I'll exit KDE and emerge from the |
| 29 |
command line over the weekend (ok, probably overly |
| 30 |
cautious, but I was burned once). |
| 31 |
|
| 32 |
Occasionally I'll get a blocking condition. I really think |
| 33 |
twice now before just unblocking via package.keywords. |
| 34 |
I've found that waiting a day or two might result in |
| 35 |
portage handling the unblocking. |
| 36 |
|
| 37 |
HTH, |
| 38 |
Roy |
| 39 |
|
| 40 |
Mark wrote: |
| 41 |
|
| 42 |
>Thanks to everyone who helped me get my system back after a couple of |
| 43 |
>world update snafus. Now of course I'm a little gun-shy about using |
| 44 |
>options like emerge --update world. So what's my best bet to keep my |
| 45 |
>system up to date, while protecting it from my own lack of |
| 46 |
>understanding of updating config files? |
| 47 |
> |
| 48 |
>Here's what I'm intending to do so far: |
| 49 |
> |
| 50 |
>1. Prior to running any large system update, back up /etc to another location |
| 51 |
>2. use dispatch-conf instead of etc-update |
| 52 |
> |
| 53 |
>Can anyone make any other suggestions? Which emerge options are best |
| 54 |
>for full system updates? Thanks |
| 55 |
> |
| 56 |
> |
| 57 |
-- |
| 58 |
gentoo-amd64@g.o mailing list |
Archives