public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benjamin Block <bebl@zlug.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] @preserved-rebuild gone in a loop
Date: Sun, 15 Dec 2013 17:37:53 +0100	[thread overview]
Message-ID: <20131215163753.GB9737@zlug.org> (raw)
In-Reply-To: <201312150952.00386.michaelkintzios@gmail.com>

On 09:51 Sun 15 Dec     , Mick wrote:
> Not sure why, but for some reason running emerge @preserved-rebuild does not 
> seem to fix some preserved libs links:
> 
> !!! existing preserved libs:
> >>> package: x11-libs/pango-1.34.1
>  *  - /usr/lib/libpangox-1.0.so.0
>  *  - /usr/lib/libpangox-1.0.so.0.3000.1
> 
> This is all caused by some hack I have in my local portage for app-
> antivirus/avast4workstation-1.3.0-r2.  No matter how many times I run 
> @preserved-rebuild the libs in question keep coming up:
> 

Most of the times, when some binary packages on my systems do cause
something like this, then I just unemerge the package that keeps
recompiling and emerge it again afterwards. This will cause the portage
to drop the library-references in question and add new ones.

So, this should do the trick:

	emerge -C app-antivirus/avast4workstation
	emerge -1 app-antivirus/avast4workstation


- Benjamin


  parent reply	other threads:[~2013-12-15 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-15  9:51 [gentoo-user] @preserved-rebuild gone in a loop Mick
2013-12-15 12:31 ` [gentoo-user] " Nikos Chantziaras
2013-12-15 12:32 ` [gentoo-user] " Neil Bothwick
2013-12-15 16:37 ` Benjamin Block [this message]
2013-12-16  4:04   ` [gentoo-user] " eroen
2013-12-16  9:28     ` Mick

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=20131215163753.GB9737@zlug.org \
    --to=bebl@zlug.org \
    --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