Re: is "postinstall fix obsolete" supposed to clean out /usr/lib?

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

On Mon, Jun 02, 2025 at 19:17:54 +0300, Valery Ushakov wrote:

> Ah, I guess the one in /usr/lib is the one that is not g/c'ed and I
> think the problem is that by the the time /usr/lib is processed, /lib
> has already been processed, so /usr/lib/libc.so.12.223 points to the
> /lib/libc.so.12.223 that no loner exists (obsoleted/deleted earlier)
> and obsolete_paths skips it

It's the other way around actually, it turns out.

When we have a library in /lib we also has symlinks in /usr/lib.
Among others we have the symlink for the actually DSO binary:

    /usr/lib/libfoo.so.1.0 -> ../../lib/libfoo.so.1.0

But exclude_libs naively/conservatively chops symlink targets to just
the basename, so from the above symlink it concludes that
libfoo.so.1.0 has something that points to it, never mind that that
libfoo.so.1.0 is actually in /lib, not in /usr/lib.  And so
exclude_libs thinks the /usr/lib/libfoo.so.1.0 is not obsolete and
should be excluded from the purge.

-uwe