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