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 1Je6yN-0006hu-3J for garchives@archives.gentoo.org; Tue, 25 Mar 2008 11:05:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ECF4CE05CA; Tue, 25 Mar 2008 11:05:41 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by pigeon.gentoo.org (Postfix) with ESMTP id A7D9CE05CA for ; Tue, 25 Mar 2008 11:05:41 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Je6y6-0003eb-Uo for gentoo-amd64@lists.gentoo.org; Tue, 25 Mar 2008 11:05:30 +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 11:05:26 +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 11:05:26 +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 11:05:07 +0000 (UTC) Message-ID: References: <5bdc1c8b0803241625r126ee324k5e96820984d501d3@mail.gmail.com> <5bdc1c8b0803241822v267dcacl64108b01cf53b3b4@mail.gmail.com> <5bdc1c8b0803242145le54b0c9we8ba99a79c5c9f9@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: 0ce69fa7-db5e-4537-b956-ff4f1f9c3f89 X-Archives-Hash: b10a28ef89411ebfb47b67cb4ecfa36e "Mark Knecht" posted 5bdc1c8b0803242145le54b0c9we8ba99a79c5c9f9@mail.gmail.com, excerpted below, on Mon, 24 Mar 2008 21:45:30 -0700: > Well, my experience is a bit different than yours. I'm sure the way I > maintain my systems, reading between your lines, is almost certainly > more lax than you care for. I do an emerge -DuN system in general about > once a week, but emerge -DuN world isn't going to happen any more often > than once every 6-8 weeks here. I don't have time to deal with the > issues that come up with all this stuff to do it more than maybe 5-6 > times per year. Even that often is pushing it, but it's about what I do= . Well, if you note, I didn't push the --deep (=3D -D). That'll save you=20 some, but at the expense of rather more pain (including a longer revdep- rebuild list since you'll likely have every dependency on the library=20 listed by then, instead of just a couple) when you /do/ eventually update= =20 those deep dependencies. I'd say do the system once a week, do the world every couple weeks,=20 always do a revdep-rebuild after the world and keep your --depclean up to= =20 date so the revdep-rebuild isn't rebuilding dependencies you don't even=20 need any more, but don't worry too much about --deep, especially on=20 primarily stable systems (like the myth boxes you mention). =20 Also, there's certainly less reason to worry about updates on machines=20 that don't do Internet and/or don't hold private data (as may be the case= =20 with some of your myth boxes) anyway. Six weeks or two months is still=20 pushing it and may lead to a lot of pain when you /do/ upgrade such=20 internal boxes, but there's no urgency other than that. > My experience with revdep-rebuild is that it wants to build some old > things, but then these things have been removed from portage and it > cannot, so I have to start looking for solutions. That requires reading > and thinking so it gets put on the back burner. That's really part of the pain of not upgrading frequently enough. As=20 such, it's avoidable. Upgrade before something is removed, and you won't= =20 have that problem. Of course, there's a trade-off here between --deep=20 and this pain, as well. If you don't use --deep, you'll encounter this=20 problem relatively more frequently. However, it's a trade-off that's up=20 to you. > The other reason I'll almost NEVER do a real emerge -DuN world is that > we use MythTV here. We have 5 machines that run Myth, either as front > ends or back ends. Unfortunately, with Myth if you update the server yo= u > have to update every machine on the network which causes problems for > the family so I don't do it. You have multiple machines. Are you making use of binary packages? =20 Assuming you use portage, FEATURES=3Dbuildpkg on your first upgraded=20 machine, with all machines set to use the same PKGDIR and using emerge=20 --usepkgonly (-K) on everything but the first one (at least where USE=20 flags are the same, and assuming compatible machine and instruction=20 types) should be a real boon to you. IOW, if you are recompiling the package for each machine it's deployed=20 on, you are wasting way more time and energy on that than you are saving=20 by updating so infrequently. If it's possible to do the build once and=20 use it on multiple machines, it's very likely worth doing so, even if it=20 means modifying USE flags and CFLAGS/CXXFLAGS a bit so you /can/ use a=20 common binary. That could just make the upgrades on those myth machines=20 much less trouble for you. Even if my "big" machine was amd64 and the others were x86, as just might= =20 be your case, I'd still consider FEATURES=3Dbuildpkg, and either decide t= o=20 run the big machine at 32-bit, or run it 64-bit but with a 32-bit chroot,= =20 so it could still could build the binaries for the others. (Of course,=20 for same machine arch, you could also run distcc if desired, but that's=20 getting to be less of an advantage as quad-core multi-gig memory machines= =20 work their way into the mainline.) > revdep-rebuild today wanted to rebuild 16 apps. To me that's lots and > lots. Maybe not to you. Well, I'd call that "lots", but not "lots and lots". =3D8^) "Lots and=20 lots" would to me start at say a couple dozen, so 24, maybe 30. =20 Certainly, a KDE upgrade, typically 90-120 packages on my machine, would=20 qualify for three "lots", tho I'd more likely term it "a hundredish"=20 packages. Interesting how such words mean slightly different things to different=20 people, isn't it? =3D8^) --=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