public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Please explain why this new 'emerge @preserved-rebuild' is good?
Date: Thu, 8 Jan 2009 10:24:01 -0800	[thread overview]
Message-ID: <5bdc1c8b0901081024x5576722qb4317d17e16bef9b@mail.gmail.com> (raw)
In-Reply-To: <b79f23070901081007u1b81f8c7m80f55d1547f0afe3@mail.gmail.com>

On Thu, Jan 8, 2009 at 10:07 AM, James Ausmus <james.ausmus@gmail.com> wrote:
<SNIP>
>>
>> Right now I'm seeing that @preserved-rebuild and revdep-rebuild want
>> to do different things. revdep-rebuild is rebuilding nss which may or
>> may not fail. @preserved-rebuild wanted to rebuild eveolution which
>> did fail.
>
> I would suggest performing the revdep-rebuild first, then doing the
> @preserved-rebuild - if revdep-rebuild is coming up with broken packages,
> those broken packages can actually prevent other packages (such as
> evolution) from building properly.
> -James
>

We'll see how it works out. I've done the revdep-rebuild.
@preserved-rebuild failed last night but is running again. If it
continues to fail I'll file a bug report.

I don't use evolution. It's just caught up in the emerge gnome stuff
and the gnome-light construct stopped working a while back so
evolution has been there not causing trouble (other than build
time/disk space) until now.

- Mark



  reply	other threads:[~2009-01-08 18:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 17:20 [gentoo-user] Please explain why this new 'emerge @preserved-rebuild' is good? Mark Knecht
2009-01-08 17:42 ` Graham Murray
2009-01-08 17:51   ` Mark Knecht
2009-01-08 17:58     ` Neil Bothwick
2009-01-08 18:03       ` Mark Knecht
2009-01-08 18:07         ` James Ausmus
2009-01-08 18:24           ` Mark Knecht [this message]
2009-01-08 18:55             ` Mark Knecht
2009-01-08 19:23               ` James Ausmus
2009-01-08 19:29                 ` Mark Knecht
2009-01-08 19:36                   ` James Ausmus
2009-01-08 19:39                     ` Mark Knecht
2009-01-08 19:45                       ` James Ausmus
2009-01-08 19:49                         ` Mark Knecht
2009-01-08 20:02                           ` James Ausmus
2009-01-08 22:35                             ` Mark Knecht
2009-01-08 23:21                               ` James Ausmus
2009-01-08 23:56                                 ` Mark Knecht
2009-01-09  1:38                                   ` Mark Knecht
2009-01-08 17:47 ` Neil Bothwick
2009-01-08 17:52   ` Volker Armin Hemmann
2009-01-08 17:53   ` Mark Knecht
2009-01-08 18:00     ` Neil Bothwick
2009-01-08 18:05       ` Mark Knecht
2009-01-08 21:59   ` Momesso Andrea

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=5bdc1c8b0901081024x5576722qb4317d17e16bef9b@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@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