On 2/25/24 11:23, David Wolfskill wrote:
Symptom was:
albert(14.0-S)[4] sudo service named restart
Password:
named not running? (check /var/run/named/pid).
ld-elf.so.1: /usr/local/lib/libfstrm.so.0: version LIBFSTRM_0.2.0 required by
/usr/local/lib/libdns-9.18.24.so not defined
/usr/local/etc/rc.d/named: ERROR: named-checkconf for
/usr/local/etc/namedb/named.conf failed
after my weekly update (in this case, from stable/14-n266695-52d7bd8c4268
to stable/14-n266881-ff9794844f86), followed by an apparently boring
update of installed packages (via locally-built packages, built using
ports-mgmt/poudriere-devel, running in stable/14-n266881-ff9794844f86).
I managed to get around it by forcibly deinstalling fstrm-0.6.1_1
and (forcibly) installing an older fstrm-0.6.1 package (from last
week), as I had no name resolution working at all by that time. (And,
given that, a lot of other services were failing, generally in expected
ways.)
My local mirror of the ports repo is at main-n652984-cb640dd9f467.
So: What's a real fix?
I had to force a rebuild/reinstall of bind918 after the fstrm upgrade.
bind918 version should have been bumped to account for the dependency :-(
Michael
