public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: CUPS now failing with "/usr/libexec/cups/filter/foomatic-rip failed"
Date: Mon, 24 Mar 2008 21:45:30 -0700	[thread overview]
Message-ID: <5bdc1c8b0803242145le54b0c9we8ba99a79c5c9f9@mail.gmail.com> (raw)
In-Reply-To: <pan.2008.03.25.03.52.47@cox.net>

Hi Duncan

On Mon, Mar 24, 2008 at 8:52 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> "Mark Knecht" <markknecht@gmail.com> 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
>  have revdep-rebuild want to rebuild "lots and lots of stuff".  I can
>  assure you that's NOT the case here, and I don't believe it should EVER
>  be the NORMAL case on a well maintained Gentoo system.

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.

In general I look at emerge -DuN world once a week and see what's up.
Typically I'll take one major app and let everything in its dependency
tree get updated, but not the complete system. If I'm lucky, when I do
finally get to the emerge -DuN world I've already done a major app, or
maybe Gnome, so there isn't all that much to do.

While I'm sure we probably have different ideas of 'lots and lots of
stuff' I'm pretty clear that it's generally too much for me to deal
with in one step. I have work to do here and the machine is busy. 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.

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
you have to update every machine on the network which causes problems
for the family so I don't do it.

Now, it's also possible to start masking things to hide some of these
issues. I'll do that with something like Myth for 2-3 months, maybe
longer, and then finally have to spend a few days updating all the
machines.

revdep-rebuild today wanted to rebuild 16 apps. To me that's lots and
lots. Maybe not to you.

Thanks,
Mark
-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-25  4:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 23:25 [gentoo-amd64] CUPS now failing with "/usr/libexec/cups/filter/foomatic-rip failed" Mark Knecht
2008-03-25  1:22 ` [gentoo-amd64] " Mark Knecht
2008-03-25  3:52   ` Duncan
2008-03-25  4:45     ` Mark Knecht [this message]
2008-03-25 11:05       ` Duncan
2008-03-25 11:16         ` Duncan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bdc1c8b0803242145le54b0c9we8ba99a79c5c9f9@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox