public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: zless <zless@dmesg.site>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerge @preserved-rebuild failure
Date: Sat, 06 Jan 2018 23:42:21 +0200	[thread overview]
Message-ID: <2703216.2rPtTa19zP@matrics> (raw)
In-Reply-To: <3a132e24-a5a9-69c6-1066-7c8a796cbc6b@hfigge.myfqdn.de>

În ziua de sâmbătă, 6 ianuarie 2018, la 23:25:32 EET, Hartmut Figge a scris:
> zless:
> >Could you also take a look at the file
> >/var/lib/portage/preserved_libs_registry ?
> 
> hafi@i5-64 ~ $ cat /var/lib/portage/preserved_libs_registry
> {
>     "sys-libs/readline:0": [
>         "sys-libs/readline-7.0_p3",
>         "10658",
>         [
>             "/lib64/libreadline.so.6.3",
>             "/lib64/libreadline.so.6"
>         ]
>     ]
> 

To me this reads as readline-7.0_p3 depends on libs from readline-6.3.

Smells a bit as some sort of bug. Try rebuilding readline?

This didn't happen here when readline was bumped.


> >It's like this when there are no preserved libs:
> >
> ># cat preserved_libs_registry
> 
> I'm currently running 'find . -name '*preserved*' on / in the hope of
> finding the set with the preserverd libs *g* Well, I will let it continue.
> 
> Hartmut






  reply	other threads:[~2018-01-06 21:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-06 20:21 [gentoo-user] emerge @preserved-rebuild failure Hartmut Figge
2018-01-06 20:40 ` Neil Bothwick
2018-01-06 21:04   ` [gentoo-user] " Hartmut Figge
2018-01-06 21:16     ` zless
2018-01-06 21:25       ` Hartmut Figge
2018-01-06 21:42         ` zless [this message]
2018-01-06 21:51           ` Hartmut Figge
2018-01-06 21:57             ` zless
2018-01-07  1:09           ` Mart Raudsepp
2018-01-07  8:14             ` Hartmut Figge
2018-01-07 13:36             ` zless

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=2703216.2rPtTa19zP@matrics \
    --to=zless@dmesg.site \
    --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