On Mon, Oct 14, 2024 at 07:19:06AM +0200, Peter wrote: > On Sun, Oct 13, 2024 at 10:55:52PM +0100, Niall O'Reilly wrote: > ! FYI only. I've submitted a [bug report][] to the FreeBSD Bugzilla. > > ! After upgrading to 1.4.1_6, I see: > ! > ! ``` > ! grab(maint)$ uname -a > ! FreeBSD grab.no8.be 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 GENERIC amd64 > ! grab(maint)$ pkg info protobuf-c | grep -i ^version > ! Version : 1.4.1_6 > ! grab(maint)$ dig -v > ! ld-elf.so.1: /usr/local/lib/libprotobuf-c.so.1: version LIBPROTOBUF_C_1.0.0 > ! required by /usr/local/lib/bind-tools/libdns-9.20.2.so not defined > ! grab(maint)$ > ! ``` > > I cannot reproduce: > > # dig -v > DiG 9.20.2 > # ldd /usr/local/bin/dig | grep protobuf > libprotobuf-c.so.1 => /usr/local/lib/libprotobuf-c.so.1 > (0x174f307b6000) > # pkg which /usr/local/lib/libprotobuf-c.so.1 > /usr/local/lib/libprotobuf-c.so.1 was installed by package protobuf-c-1.4.1_6 > > # uname -a > FreeBSD vbuild3 13.4-RELEASE-p1 FreeBSD > 13.4-RELEASE-p1[e0f62d90381c=bc3877972ebd+41] ZE6R13V1 amd64
Peter, in your reproduce attempt, were these newly-installed (presumably together), or was protobuf[-c] subsequently upgraded in an existing installation? In a quick experiment, which had bind 9.18.30 btw, I was unable to reproduce the problem in a fresh install of bind or bind-tools, either FreeBSD pkg pulls in the protobuf[-c] pre-req pkg during install. However, on 4 servers (3 amd64, 1 i386) which had pre-existing bind and bind-tools pkgs already installed, upgrading protobuf[-c] yielded the lib problem Niall saw, e.g. for both 'dig' and 'named' binaries. Re-installing bind[-tools] resolved the library conflict. I don't quite understand why. sr. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
