Opened 12 years ago
Closed 9 years ago
#36526 closed defect (worksforme)
docbook-xml-5.0 deactivate errors
Reported by: | nerdling (Jeremy Lavergne) | Owned by: | lockhart (Thomas Lockhart) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | docbook-xml-5.0 |
Description
When performing a deactivate active
, docbook-xml-5.0 produced errors:
:info:deactivate xmlcatmgr: no matching entry for = `/opt/local/share/xml/docbook/5.0/docbook.cat' of type `CATALOG' :info:deactivate Command failed: xmlcatmgr -s -c = /opt/local/etc/sgml/catalog remove CATALOG = /opt/local/share/xml/docbook/5.0/docbook.cat
Change History (5)
comment:1 Changed 12 years ago by lockhart (Thomas Lockhart)
comment:2 Changed 12 years ago by nerdling (Jeremy Lavergne)
I suspect checking that the file exists first is the easiest way to wrap your command. I'd use Tcl's commands to check this, and maybe if you need to wrapping it with a catch.
comment:3 Changed 10 years ago by mojca (Mojca Miklavec)
Owner: | changed from lockhart@… to tlockhart1976@… |
---|---|
Version: | 2.1.99 |
comment:4 Changed 9 years ago by lockhart (Thomas Lockhart)
Current ports cannot reproduce the problem:
sudo port uninstall docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 iso8879 docbook-xml-4.2 openjade docbook-sgml-4.2 docbook-utils p5.22-sgmlspm docbook-dsssl docbook-xml-5.0 docbook-xsl docbook-xsl-ns sgml-common sudo rm -rf /opt/local/etc/sgml /opt/local/etc/xml sudo port install docbook-xml-5.0 sudo port deactivate docbook-xml-5.0
I believe that this problem report should be retired.
comment:5 Changed 9 years ago by nerdling (Jeremy Lavergne)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Agreed. Works for me now as well.
Note: See
TracTickets for help on using
tickets.
OK, I see how this can happen I think. There is a "post-deactivate" phase which removes items from the catalogs. istm that this is most properly fixed by changing this to "pre-deactivate" so we can test whether the files mentioned in the catalog actually exist, and only if so then try removing the entries. Advice is appreciated, but in the meantime will test a fix involving using pre-deactivate.