From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NpU08-0004Vu-Jz for garchives@archives.gentoo.org; Wed, 10 Mar 2010 22:03:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 393ECE0CBB for ; Wed, 10 Mar 2010 22:03:36 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by pigeon.gentoo.org (Postfix) with ESMTP id 0A669E0CAA for ; Wed, 10 Mar 2010 21:34:42 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NpTY5-0001D2-7y for gentoo-amd64@lists.gentoo.org; Wed, 10 Mar 2010 22:34:37 +0100 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Mar 2010 22:34:37 +0100 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Mar 2010 22:34:37 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: Failures on updating KDE to 4.4.1 - unable to update kmail Date: Wed, 10 Mar 2010 21:34:23 +0000 (UTC) Message-ID: References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies) Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 17127ca9-34a9-45ba-8a49-b62000181247 X-Archives-Hash: 36db3549fb11a83fa4b57a33459a5e69 Paul Stear posted on Wed, 10 Mar 2010 08:05:32 +0100 as excerpted: > I have just un-installed amarok and am starting to upgrade world > including mysql etc. One additional thing I should mention. For me it's routine so sometimes = I=20 forget that it may not be that way for everyone. The scriptlets I normally use to upgrade all use -NuD, so an update is=20 always a FULL update, all the way thru the dependencies (deep), and=20 updating any packages with changed USE flags as well. Personally, I don'= t=20 have much use for half-way updates, as I believe they'll cause me more=20 pain than the time they'll save. Similarly, I always finish with a scriptlet that runs lafilefixer --justfixit, and then revdep-rebuild $* -- -a1. (Actually, it's slightly= =20 more complicated than that, as I source a config file that sets a paralle= l=20 jobs environmental variable, and add that variable to the revdep-rebuild=20 command line as well, so it takes advantage of portage's parallel emerge=20 features where it can.) Of course, Between lafilefixer and the fact that= =20 I run as-needed in my LDFLAGS, my revdep-rebuild load is far lower than i= t=20 would be otherwise, which helps. =3D:^) Then another scriptlet runs emerge --ask --depclean, and if it cleaned=20 anything major, I run the rebuild scriptlet again just to double-check=20 that the removals didn't leave any hanging needed rebuilds. Of course, another scriptlet takes care of the etc-updates. So when I'm done, not only are all dependencies deep updated along with=20 all packages with new USE flags, but I've ensured all stale linkages are=20 fixed and removed all the old no longer depended packages as well,=20 rerunning the stale linkages check after the cruft removal. I also take care to read all the elogged messages (or at least skim them,= =20 as most are repeats I'm familiar with by now) and do all the config=20 updates. I'm unsure how many problems such a thoroughly proactive update regime=20 saves me, but I'm sure it's non-zero. If you're not regularly running=20 revdep-rebuild after updates, try it, with --ask or --pretend first, as=20 you may have quite a few rebuilds built up the first time you run it. Th= e=20 --newuse and --deep emerge flags are mostly me being extra cautious (plus= =20 I just like being updated thru and thru), as in theory they shouldn't be=20 needed. But it shouldn't need stated that theory doesn't always match=20 reality. And if you're not running emerge --depclean routinely, do be=20 extremely careful the first few times you run it, absolutely run it with --pretend the first time, and go thru its list looking for stuff you want= =20 to keep and add it to your world file (emerge --select --noreplace),=20 before running --depclean for real. Removing that cruft does help becaus= e=20 sometimes packages get mixed up and link to the old versions, if they're=20 still around. Plus, there's potential security vulns to think about,=20 since they're no longer in the dependency tree portage checks for updates= . Using such a program, you should proactively avoid many problems, and the= n=20 you'll be the one shrugging your shoulders and saying "it works for me."=20 =3D:^) Of course it won't fix them all, but the ones that are left are m= uch=20 more likely to have real bugs associated with them, not the fuzzy bugs=20 associated with a system not kept in peak running order. (Also keep in mind that perl-cleaner and python-updater are the parallel=20 to revdep-rebuild in their respective language domains. But unless you'r= e=20 doing python/perl development or scripting on your own, it's unlikely=20 you'll need them as often as revdep-rebuild, as the number of apps using=20 them isn't as high, and the usage isn't as "system-core", as C/C++.) --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman