xmlcharent-0.3_2 and iso8879-1986_3 package reinstalls: "pkg: POST-INSTALL script failed"? vs. @xmlcatmgr and Keywords/xmlcatmgr.ucl

[Matthias Andree]

Am 11.10.18 um 17:39 schrieb Mark Millard via freebsd-toolchain:
> In updating a powerpc64 context after a poudriere-devel bulk run, I
> got the following from pkg upgrade . . .
> 
> Installed packages to be REINSTALLED: 	xmlcharent-0.3_2 (ABI changed: 'freebsd:12:powerpc:64' -> 'freebsd:12:*')
> . . .
> 	iso8879-1986_3 (ABI changed: 'freebsd:12:powerpc:64' -> 'freebsd:12:*')
> . . .
> 
> [127/181] Extracting iso8879-1986_3: 100%
> xmlcatmgr: entry already exists for `/usr/local/share/sgml/iso8879/catalog' of type `CATALOG'
> pkg: POST-INSTALL script failed
> 
> . . .
> 
> [138/181] 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
> 
> The context is a personal head-based -r339076 buildworld
> buildkernel (it was cross built) and ports being updated
> based on -r480180 .
> 
> Is there anything that I should do because of the messages?

Mark, no need, it seems the failure is harmless on upgrades.

It appears to be a bug in the @xmlchatmgr lines for pkg-plist files, and
I have seen these xmlcatmgr complaints you are showing for ages on all
ports that install SGML or XML catalogs when they are upgraded, if you
manually deinstall (pkg delete -f) and reinstall these ports, they do
not appear.

I question the ports/Keywords/xmlcatmgr.ucl and wonder if what is
currently labelled a post-deinstall action should become a pre-deinstall
action - and unfortunately, I have not found documentation on this so
cannot propose a patch.  Possibly we also need a pre-/post-upgrade
action pair to solve this.

Baptiste, any insights?