From: zless <zless@dmesg.site>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerge @preserved-rebuild failure
Date: Sun, 07 Jan 2018 15:36:56 +0200 [thread overview]
Message-ID: <2113503.McqP9FOfaP@matrics> (raw)
In-Reply-To: <1515287372.2071.3.camel@gentoo.org>
În ziua de duminică, 7 ianuarie 2018, la 03:09:32 EET, Mart Raudsepp a scris:
> > 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.
>
> This is no bug here. It's just storing the fact that it preserved these
> /lib64/libreadline.so.6{,.3} under the replacing newer version package.
> That is, readline-7.0_p3 now owns these files, but based on this
> registry, they will be deleted and removed from its CONTENTS, once
> there are no more consumers of it based on essentially NEEDED.ELF.2
> contents in the VDB (/var/db/pkg/*/*/NEEDED.ELF.2).
> That is, what is keeping them from being removed is not stored in this
> registry.
Thanks for the in-depth explanation. Do you think that revdep-rebuild would've
helped here?
And a bit off-topic for this thread (but it's a subject that interests me):
does the preserved rebuild feature track user installed programs (outside of
portage control)?
prev parent reply other threads:[~2018-01-07 13:37 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
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 [this message]
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=2113503.McqP9FOfaP@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