pkg_add goofiness in 7.0

Kris Kennaway kris at
Tue Apr 1 03:09:02 PDT 2008

perryh at wrote:
> ...
>>> extract: execute '/usr/local/bin/xmlcatmgr -sc /usr/local/share/sgml/catalog.ports add linuxdoc/catalog'
>>> xmlcatmgr: unbalanced arguments for `add' action
>>> pkg_add: command '/usr/local/bin/xmlcatmgr -sc /usr/local/share/sgml/catalog.ports add linuxdoc/catalog' failed
> ...
>> That looks like a warning from xmlcatmgr which may or may not be 
>> important, but the package apparently added itself completely (no
>> errors were reported by pkg_add).
> It may not make a lot of difference, but I am now wondering how to
> recognize an "error reported by pkg_add" since this:
>>> pkg_add: command '/usr/local/bin/xmlcatmgr -sc /usr/local/share/sgml/catalog.ports add linuxdoc/catalog' failed
> looks like one to me, but apparently it isn't.

/usr/local/* files are installed by a package, in this case run as part 
of a particular package installation script, and this failure is 
dutifully reported by pkg_add.

> Just taking the xmlcatmgr message at face value, it looks as if
> some addition that linuxdoc intended to make in some catalog did
> not get done.  Anything following that step in the postinstall
> script may also not have gotten done.  My gut suspicion is that
> there is something wrong with the linuxdoc postinstall script
> -- or perhaps linuxdoc has an unstated dependency which I don't
> happen to have installed -- rather than something wrong with
> xmlcatmgr.  PR time, I guess :(

Yes, that is the next step.  It works for many others though, so the 
problem is likely to be more subtle than "it is completely broken".


More information about the freebsd-questions mailing list