public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can't find libdbus-1.so.2 ?
Date: Sun, 17 Sep 2006 16:11:44 +0100	[thread overview]
Message-ID: <200609171613.08540.michaelkintzios@gmail.com> (raw)
In-Reply-To: <200609171453.37086.bo.andresen@zlin.dk>

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

On Sunday 17 September 2006 13:53, Bo Ørsted Andresen wrote:
> On Sunday 17 September 2006 13:09, Mick wrote:
> > I think the OP meant that revdep completes without anything proposed for
> > remerging, but with a long list of errors reported.
>
> If that is correct then it means that the OP is seeing old cruft.
> revdep-rebuild with or without --library isn't going to fix that. Cleaning
> the old cruft (after checking that it is in fact cruft) is the proper
> solution for that...

Yes, all things being equal.  But in reality emerges don't always complete 
cleanly when your system crashes half way.  Should that be the case 
revdep-rebuild-ing it will ensure that all is put right with regards to 
dependencies before old libs are deleted.
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-09-17 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17  2:59 [gentoo-user] can't find libdbus-1.so.2 ? Chuanwen Wu
2006-09-17  8:15 ` Neil Bothwick
2006-09-23  1:52   ` Chuanwen Wu
2006-09-23  2:05     ` Bo Ørsted Andresen
2006-09-23  2:34       ` Chuanwen Wu
2006-09-23  3:13         ` Bo Ørsted Andresen
2006-09-23  5:29           ` Chuanwen Wu
     [not found] ` <200609171209.58379.michaelkintzios@gmail.com>
     [not found]   ` <200609171453.37086.bo.andresen@zlin.dk>
2006-09-17 15:11     ` Mick [this message]
2006-09-23  2:07 ` [gentoo-user] " Chuanwen Wu

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=200609171613.08540.michaelkintzios@gmail.com \
    --to=michaelkintzios@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