Note: libutil.so bump from main-n279246-0c381b7f0570
- Reply: John Kennedy : "Re: Note: libutil.so bump from main-n279246-0c381b7f0570"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 03 Aug 2025 13:50:03 UTC
TL;DR: You may want to keep a copy of /lib/libutill.so.9 around for a bit. Details: I track both stable/14 & head daily on a few machines, one of which is the laptop I use for everyday use. [Caveat: I am not recommending this approach for others; it seems to generally work OK for me.] As part of this, I also run "make delete-old-libs" as a late step of each update. To enable me to actually use the laptop (vs. spending full time rebuilding software to run it), I build the ports under stable/14 and have the /usr/local file system shared between them. One of the ports on which I depend is security/sudo, which depends on libutil.so. Since sudo is built under stable/14, it expects to find libutil.so.9. Following main-n279246-0c381b7f0570, head has /lib/libutil.so.10 in place of libutil.so.9. Today's update of head for me was from main-n279245-d1095367eb51 to main-n279267-877e70e6087f, which includes main-n279246-0c381b7f0570. While I have the misc/compat14x port (maintainer Cc:ed) installed, it does not (as of this writing) provide libutil.so.9. As a mitigation, I copied libutil.so.9 from the stable/14 slice to /usr/local/lib/compat; that allowed sudo to work in both stable/14 and head. (On one of the machines, I even managed to do this proactively.) Peace, david -- David H. Wolfskill david@catwhisker.org Of course firing the statistician will force the statistics to conform! See https://www.catwhisker.org/~david/publickey.gpg for my public key.