[gentoo-user] Portage reports preserved libs, but won't rebuild

[Matt Connell]

First time I've seen this happen!

Any time I emerge anything, I get portage telling me I have the
following preserved libs:

---

package: app-arch/bzip2-1.0.8-r4

* - /usr/lib/libbz2.so.1
* - /usr/lib/libbz2.so.1.0.8
* used by /usr/lib/libfreetype.so.6 (preserved)
* used by /usr/lib/libfreetype.so.6.20.1 (preserved)

package: dev-libs/glib-2.76.4

* - /usr/lib/libglib-2.0.so.0
* - /usr/lib/libglib-2.0.so.0.7600.4
* used by /usr/lib/libharfbuzz.so.0 (preserved)
* used by /usr/lib/libharfbuzz.so.0.60801.0 (preserved)

package: dev-libs/libpcre2-10.42-r1

* - /usr/lib/libpcre2-8.so.0
* - /usr/lib/libpcre2-8.so.0.11.2
* used by /usr/lib/libglib-2.0.so.0 (preserved)
* used by /usr/lib/libglib-2.0.so.0.7600.4 (preserved)

package: media-gfx/graphite2-1.3.14_p20210810-r3

* - /usr/lib/libgraphite2.so.3
* - /usr/lib/libgraphite2.so.3.2.1
* used by /usr/lib/libharfbuzz.so.0 (preserved)
* used by /usr/lib/libharfbuzz.so.0.60801.0 (preserved)

package: media-libs/freetype-2.13.2

* - /usr/lib/libfreetype.so.6
* - /usr/lib/libfreetype.so.6.20.1
* used by /usr/lib/libharfbuzz.so.0 (preserved)
* used by /usr/lib/libharfbuzz.so.0.60801.0 (preserved)

package: media-libs/harfbuzz-8.2.0

* - /usr/lib/libharfbuzz.so.0
* - /usr/lib/libharfbuzz.so.0.60801.0
* used by /usr/lib/libfreetype.so.6 (preserved)
* used by /usr/lib/libfreetype.so.6.20.1 (preserved)

package: media-libs/libpng-1.6.40-r1

* - /usr/lib/libpng16.so.16
* - /usr/lib/libpng16.so.16.40.0
* used by /usr/lib/libfreetype.so.6 (preserved)
* used by /usr/lib/libfreetype.so.6.20.1 (preserved)

package: sys-libs/zlib-1.3-r1

* - /usr/lib/libz.so.1
* - /usr/lib/libz.so.1.2.13
* used by /usr/lib/libfreetype.so.6 (preserved)
* used by /usr/lib/libfreetype.so.6.20.1 (preserved)
* used by /usr/lib/libpng16.so.16 (preserved)
* used by /usr/lib/libpng16.so.16.40.0 (preserved)

---

But when I run emerge @preserved-rebuild as one should, all I get is:
"Nothing to merge; quitting."

Anyone else experienced this? How do I figure out what I need to do?

Thanks in advance.

[Matt Connell]

Sorry for the double post; I got a mail-undeliverable from Google so I
thought it didn't go through and retried it. Turns out it got to the
mailing list (both times) but not to gmail recipients because Google
doesn't like my SPF record (record says hard-fail on no match and
someone somewhere is using ipv6).

[Nuno Silva]

Post by Matt Connell
Sorry for the double post; I got a mail-undeliverable from Google so I
thought it didn't go through and retried it. Turns out it got to the
mailing list (both times) but not to gmail recipients because Google
doesn't like my SPF record (record says hard-fail on no match and
someone somewhere is using ipv6).

No, it's definitely not a problem at your side, this is still caused by
the same user which is still subscribed using a @live.ru mailbox and
then sets it to forward to their Gmail address.

Last time I checked, Microsoft, when forwarding, pretends to be the
original sender, instead of @live.ru, which triggers the failure you see
from Gmail.

In the details in the error/failure message the only thing that refers
to you will likely be your address. The IP address which tried to
send the message to Google belongs to Microsoft.