Re: is "postinstall fix obsolete" supposed to clean out /usr/lib?
Valery Ushakov <[email protected]> Mon, 2 Jun 2025 19:17:54 +0300
| Newsgroups | gmane.os.netbsd.devel.toolchain |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jun 02, 2025 at 18:56:33 +0300, Valery Ushakov wrote: > On Mon, Jun 02, 2025 at 17:20:30 +0200, Christoph Badura wrote: > > > So "postinstall fix obsolete" cleaned out $DESTDIR/lib/libc.so.12.223 but > > left $DESTDIR/lib/libc.so.12.223 in place and then checkflist complains. > > Which one of those is really /usr/lib? :) > > > > Is that intended behaviour? > > No. I would expect both obsolete minors to get g/c'ed. 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 -uwe