From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DyA9G-00056j-1w for garchives@archives.gentoo.org; Thu, 28 Jul 2005 15:18:14 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6SFFRYT003081; Thu, 28 Jul 2005 15:15:27 GMT Received: from rwcrmhc12.comcast.net (rwcrmhc14.comcast.net [216.148.227.89]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6SFFQe0015001 for ; Thu, 28 Jul 2005 15:15:26 GMT Received: from [192.168.0.123] (pcp04370732pcs.nrockv01.md.comcast.net[69.140.218.245]) by comcast.net (rwcrmhc14) with ESMTP id <20050728151554014009b040e>; Thu, 28 Jul 2005 15:15:55 +0000 Message-ID: <42E8F6A9.50600@erols.com> Date: Thu, 28 Jul 2005 11:15:53 -0400 From: Matt Randolph User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] backups and world updates References: <1f81f7e005072806534ed43866@mail.gmail.com> In-Reply-To: <1f81f7e005072806534ed43866@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 2ec91647-252f-4e06-b5e2-21631ba8c646 X-Archives-Hash: a98189167875f9416d7b30b4188e53e6 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 > > dispatch-conf is probably the single biggest change you can make to reduce the chance of future borking (etc-update is bad news; stay away from it). If the diff from dispatch-conf shows nothing but gobbledygook before and after, then it's very likely you should simply use the new version. One thing you might do is add a comment whenever you make changes to a configuration file by hand: # added by Mark 7-28-05 foo="bar" Then the diff will show you clearly that you need to merge the files. Obviously, this won't work if the manual change was made through some utility. But then, you can probably just use that utility again to re-make the changes. One other thing I strongly recommend is that you clean up your world file. You really should have only the bare minimum number of packages in the world file to avoid problems like circular dependencies. I remember once, long ago, I had both kdebase AND the kde-meta packages in my world file (don't ask me how). I couldn't upgrade much of anything kde related until I cleared that up. Everything was blocking everything else. Use the dep script to clean up your world file. It's located here: http://forums.gentoo.org/viewtopic.php?p=907101 The one thing I would add about the dep script is that you still need to use your head when it comes to listening to it's recommendations. dep told me to remove quake3 because I had quake3-wop (which depends on quake3) and, thus, quake3 was redundant. I have decided to keep both packages in my world file because I may choose to unmerge the quake3-wop mod, but I'd probably still want to have quake3 installed. Other than in cases like that, I strongly suggest you listen to what dep tells you and consider making the recommended changes to your world file (and copy world to [.]world.bak before you make any changes, of course). I do an "emerge -Dup world" every day right after I "glsa-check." I do a "revdep-rebuild -p" whenever I wind up upgrading more than a few packages. If things go wrong during an emerge world, I have found it useful to emerge --metadata before resuming. Also, delete /root/.revdep-rebuild*.?_* if revdep-rebuild is acting strange. Then just try again. Also, bear in mind that revdep-rebuild doesn't work properly with binary packages like mozilla-firefox-bin and openoffice-bin. I always do a "revdep-rebuild -p" and then emerge the broken packages by hand. Oh, and remember to use the --oneshot flag when you're emerging a single package to fix a dependency. Otherwise, you'll wind up with redundant entries in your world file again. You'll have to keep your wits about you here again to decided whether a given package belongs in your world file or not. -- "Pluralitas non est ponenda sine necessitate" - W. of O. -- gentoo-amd64@gentoo.org mailing list