Making all in HTML make[2]: Entering directory `/var/tmp/portage/docbook-sgml-utils-0.6.11/work/docbook-utils-0.6.11/doc/HTML' SGML_CATALOG_FILES=/etc/sgml/catalog \ SGML_SEARCH_PATH=../..:../../doc:.. \ jade -t sgml -i html -d ../../docbook-utils.dsl\#html \ -V '%use-id-as-filename%' ../../doc/docbook-utils.sgml jade:/etc/sgml/openjade-1.3.cat:1:8:E: cannot open "/usr/share/sgml/openjade-1.3/catalog" (No such file or directory) jade:/etc/sgml/openjade-1.3.cat:2:8:E: cannot open "/usr/share/sgml/openjade-1.3/dsssl/catalog" (No such file or directory) The lines ... jade:/etc/sgml/openjade-1.3.cat:1:8:E: cannot open "/usr/share/sgml/openjade-1.3/catalog" (No such file or directory) jade:/etc/sgml/openjade-1.3.cat:2:8:E: cannot open "/usr/share/sgml/openjade-1.3/dsssl/catalog" (No such file or directory) repeat over and over again maybe 150 times or so... Then ... make[2]: *** [api.html] Error 1 make[2]: Leaving directory `/var/tmp/portage/docbook-sgml-utils-0.6.11/work/docbook-utils-0.6.11/doc/HTML' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/docbook-sgml-utils-0.6.11/work/docbook-utils-0.6.11/doc' make: *** [all-recursive] Error 1 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line -126, Exitcode 2 !!! (no error message) !!! emerge aborting on /usr/portage/app-text/docbook-sgml-utils/docbook-sgml-utils-0.6.11.ebuild .
ulkesh, any ideas on this one?
Edward is using OpenJade 1.3 while the latest version is 1.3.1. Maybe docbook-sgml-utils should have the dependency >=app-text/openjade-1.3.1 Unfortunately I can't test this because the ebuilds of OpenJade 1.3 have been cleaned from the portage tree. Edward, could you please upgrade to OpenJade 1.3.1 to see if that fixes the problem?
That's actually what I was trying to do originally. I have openjade-1.3.1-r4 installed now (that's the only openjade version I have installed) and I get the same errors when emerging docbook-utils-0.6.11
Do you get exactly the same errors, or has '/etc/sgml/openjade-1.3.cat' been replaced by '/etc/sgml/openjade-1.3.1.cat' and '/usr/share/sgml/openjade-1.3/' by '/usr/share/sgml/openjade-1.3.1/'?
errors are ... jade:/etc/sgml/openjade-1.3.cat:1:8:E: cannot open "/usr/share/sgml/openjade-1.3/catalog" (No such file or directory) jade:/etc/sgml/openjade-1.3.cat:2:8:E: cannot open "/usr/share/sgml/openjade-1.3/dsssl/catalog" (No such file or directory) So I guess there are still references to the old openjade-1.3 stuff ... Should I remove them and from where?
I removed all opejade-1.3 references from the config files in /etc/sgml and it docbook-utils-0.6.11 emerged fine. In the case where there was a reference to only openjade-1.3 I changed it to openjade-1.3.1 ... when both were present I removed the openjade-1.3 Does that sound right?
Removing lines is usually not a good idea :) You should use 'emerge -pC openjade' to figure out which version(s) you have installed. Then uninstall any old one with 'emerge -C openjade-<version>' I just noticed that the OpenJade ebuild only installs the catalog files referenced in your error if /usr/bin/install-catalog is present. /usr/bin/install-catalog is found in app-text/sgml-common, and if you don't have that emerged, it could explain why you got those errors.
I don't have any old openjade versions installed I removed them earlier trying to figure out what was going on. I guess the line in the config files did not get removed.
Ulkesh, is there something other than install-catalog that we can do at the end of the ebuilds? Something like what I do in the dev-perl ebuilds would be cleaner, I think. Opinions?
What kind of thing are you doing in the dev-perl ebuilds exactly ? :)
well, it was brought to my attention that everytime a new thing from dev-perl got installed, the file perllocal.pod in /usr/lib/perl/somewhere got over-written, so that any given time, only ONE perl module was ever listed in there, and it had the /var/tmp/portage prefix in it. So, I redesigned the dev-perl ebuilds (in the /usr/portage/eclass/perl*.eclass files) to throw their pod entries into /usr/share/perl/gentoopods, and then at the end of each one's emerge or unmerge, the system's perllocal.pod gets rebuilt entirely with the entries in /usr/share/perl/gentoopods. Think that kinda apprach is applicable here?
btw, Ulkesh, keep in mind that I know _nothing_ about SGML and docbook etc
Well, I don't know anything about SGML and DocBook either :) Apparently install-catalog is able to add/remove entries correctly in the /etc/sgml/catalog file. Unemerging OpenJade on my system effectively removes any references to its files in the catalog. I think Edward just had this problem because the old openjade ebuild had a bug in its pkg_postrm section (but I cannot verify this and so I could be wrong). Replacing calls to install-catalog with something like what you do in dev-perl would certainly ensure that all the files referenced in the catalog _do_ exist, so it could be useful.
*** This bug has been marked as a duplicate of 4598 ***
