From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Je0Db-0002y6-DW for garchives@archives.gentoo.org; Tue, 25 Mar 2008 03:52:59 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1E732E08CA; Tue, 25 Mar 2008 03:52:58 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by pigeon.gentoo.org (Postfix) with ESMTP id C49BEE08CA for ; Tue, 25 Mar 2008 03:52:57 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Je0DV-0000wy-Mz for gentoo-amd64@lists.gentoo.org; Tue, 25 Mar 2008 03:52:53 +0000 Received: from ip68-231-12-179.ph.ph.cox.net ([68.231.12.179]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 25 Mar 2008 03:52:53 +0000 Received: from 1i5t5.duncan by ip68-231-12-179.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 25 Mar 2008 03:52:53 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: CUPS now failing with "/usr/libexec/cups/filter/foomatic-rip failed" Date: Tue, 25 Mar 2008 03:52:48 +0000 (UTC) Message-ID: References: <5bdc1c8b0803241625r126ee324k5e96820984d501d3@mail.gmail.com> <5bdc1c8b0803241822v267dcacl64108b01cf53b3b4@mail.gmail.com> 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@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-12-179.ph.ph.cox.net User-Agent: Pan/0.132 (Waxed in Black) Sender: news Content-Transfer-Encoding: quoted-printable X-Archives-Salt: d15d7aad-0f37-4c65-924b-1c799f1ea07c X-Archives-Hash: 08d628ae6f0a49d2e20dd14573cd66b0 "Mark Knecht" posted 5bdc1c8b0803241822v267dcacl64108b01cf53b3b4@mail.gmail.com, excerpted below, on Mon, 24 Mar 2008 18:22:20 -0700: >> Of course revdep-rebuild wants to rebuild lots and lots of stuff I see you solved the original problem, but this bit worries me. You used "of course", which makes it sound as if it's "natural" to you to= =20 have revdep-rebuild want to rebuild "lots and lots of stuff". I can=20 assure you that's NOT the case here, and I don't believe it should EVER=20 be the NORMAL case on a well maintained Gentoo system. Once in a very=20 long time, there may be individual upgrade cases where it happens because= =20 half the system depends on the upgraded library and the upgrade changed=20 the ABI, the upgrade to expat-2 I believe it was comes to mind, but once=20 that rebuild is done (and I'd say two weeks is plenty of time for that),=20 it should be months, likely years, before any more more than perhaps a=20 half dozen to a dozen packages (max) ever appear together at once on a=20 revdep-rebuild. I think it has been since that expat upgrade that I've=20 ever had a half dozen items listed at once in revdep-rebuild here, and I=20 even doubled that above, to a dozen, for those that run a bit sloppier=20 installation than I. I'd recommend that people do a world upgrade every couple of weeks=20 minimum (noting that if you do it every week or every few days, you'll=20 have less to upgrade all at once), always do an etc-update (or equivalent= =20 if using a different tool) after merging anything, just to be sure, and=20 do a revdep-rebuild also at least every couple weeks, again noting that=20 doing it more often means less stuff at once to worry about. That, plus=20 a regular (say once a month or so minimum) emerge --newuse, revdep- rebuild, emerge --depclean, and another revdep-rebuild just to be sure=20 after the depclean, will help keep the system clean and well maintained,=20 and that "Of course revdep-rebuild wants to rebuild lots and lots of=20 stuff" problem should become a thing of the past. =3D8^) Of course, don't forget the --pretend first, especially on --depclean,=20 but really on all the above, so you have some idea of what it's going to=20 do and can add packages to your world file or whatever if necessary. And= =20 again, those are what I'd recommend as minimums. Remember that if you do= =20 it more frequently, you have far less to deal with at once, making the=20 job far easier. =3D8^) =20 It's just that "revdep rebuild wants to rebuild lots and lots of stuff"=20 should be a very unusual event, not EVER an "of course" event If that's=20 NOT the case, if it HAS become an "of course" event, it's simply because=20 someone has been slacking. While it'll only mean minor stuff broken on a= =20 day to day basis, sooner or later it'll catch up to you, either with a=20 compound failure so large it's difficult to recover from (a broken gcc=20 making it impossible to recompile anything to fix it, for instance, or a=20 broken python making it impossible to emerge anything), or with an old=20 and stale package you've forgotten about getting a security vuln that=20 someone takes advantage of, and you get cracked. (Yeah, I know that some folks don't upgrade for six months or more at a=20 time... I never really understood why these folks bother to run Gentoo,=20 as at that point, it's likely going to be easier doing the binary=20 distribution update thing, with upgrades coming out about every six=20 months, than trying to do an upgrade a piece at a time on Gentoo, without= =20 breaking anything vital in the process. Yes, it's possible to do six=20 month upgrades on Gentoo, just like it's possible to only install the=20 binary packages on the release and package media and never compile=20 anything, but it's really not /designed/ for that, and there are other=20 distributions that handle those usage cases rather better, so Gentoo's a=20 rather poor choice for them.) --=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 --=20 gentoo-amd64@lists.gentoo.org mailing list