From a typescript of an upgrade: [173/951] Extracting xmlcharent-0.3_2: 100% xmlcatmgr: entry already exists for `/usr/local/share/xml/xmlcharent/catalog' of type `CATALOG' xmlcatmgr: entry already exists for `/usr/local/share/xml/xmlcharent/catalog.xml' of type `nextCatalog' pkg: POST-INSTALL script failed
Created attachment 255975 [details] partial context 2024-12-20_04-20-typescript.txt abbreviated for 283434.txt is taken from my local record of the session: 2024-12-20_04-20-typescript.txt The full typescript file (more than 68,000 lines) is available on request. In a nutshell: root@pkg:~ # freebsd-version -kru ; uname -aKU 14.1-RELEASE-p5 14.1-RELEASE-p5 13.3-RELEASE-p8 FreeBSD pkg 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 GENERIC amd64 1401000 1303001 root@pkg:~ # /usr/sbin/freebsd-update install … – for userland to be at 14.1-RELEASE-p6. Then package upgrades. I was tempted to restart the OS before upgrading packages, however from <https://www.freebsd.org/releases/14.1R/installation/#upgrade-binary> it seems (to me) that package upgrades may be attempted before a restart, so I experimented with this approach.
I should add: a) xmlcharent was amongst the packages to be reinstalled for the change in ABI, with no change no to the version (0.3_2 in this case) xmlcharent-0.3_2 (ABI changed: 'freebsd:13:*' -> 'freebsd:14:*') b) post-install scripts also failed for the port packages below. iso8879-1986_3 sdocbook-xml-1.1_2 docbook-sgml-4.5_1 docbook-xml-5.0_3 docbook-xsl-1.79.1_1,1 I have no immediate plan to make reports for any of those five. Let's see how this bug 283434 progresses. Thank you
Created attachment 255976 [details] Screenshot: reproducing the issue Re: comment #1 > … tempted to restart the OS before upgrading packages, … It's a VirtualBox guest, so I tried that. The same symptom (pictured).