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:03:36 -0800	[thread overview]
Message-ID: <5bdc1c8b0901081003j72b07cdfve2247ff81cdd3dc2@mail.gmail.com> (raw)
In-Reply-To: <20090108175825.0584e0a4@krikkit>

On Thu, Jan 8, 2009 at 9:58 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 8 Jan 2009 09:51:32 -0800, Mark Knecht wrote:
>
>> I guess then that the constant messages about doing an emerge
>> @preserved-rebuild aren't necessarily to be followed, or at least not
>> worried about if they fail as whatever program needs the libraries
>> still has the old versions?
>
> They should be followed and the problem fixed. Not only is it untidy
> leaving old copies of libraries around but, as Volker says, the old
> versions can prevent revdep-rebuild working correctly.
>
>
> --
> Neil Bothwick

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'm somewhat unclear as to how to proceed. Using emerge is currently
telling me I should do an emerge -e world to fully take advantage of
new features in portage-2.2. I guess that message wouldn't be there
unless it was really a good thing to do but that's a lot of downtime
for me.

- Mark



  reply	other threads:[~2009-01-08 18:03 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 [this message]
2009-01-08 18:07         ` James Ausmus
2009-01-08 18:24           ` Mark Knecht
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=5bdc1c8b0901081003j72b07cdfve2247ff81cdd3dc2@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