Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 4618 - docbook-utils-0.6.11 emerge fails
Summary: docbook-utils-0.6.11 emerge fails
Status: RESOLVED DUPLICATE of bug 4598
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Seemant Kulleen (RETIRED)
Depends on:
Reported: 2002-07-06 11:31 UTC by Edward Muller
Modified: 2005-07-17 13:06 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Edward Muller 2002-07-06 11:31:03 UTC
Making all in HTML
make[2]: Entering directory
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/ cannot open
"/usr/share/sgml/openjade-1.3/catalog" (No such file or directory)
jade:/etc/sgml/ cannot open
"/usr/share/sgml/openjade-1.3/dsssl/catalog" (No such file or directory)

The lines ...
jade:/etc/sgml/ cannot open
"/usr/share/sgml/openjade-1.3/catalog" (No such file or directory)
jade:/etc/sgml/ 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
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
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 .
Comment 1 Seemant Kulleen (RETIRED) gentoo-dev 2002-07-06 17:12:08 UTC
ulkesh, any ideas on this one?
Comment 2 Julien Herran 2002-07-06 17:39:59 UTC
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?
Comment 3 Edward Muller 2002-07-06 17:47:52 UTC
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

Comment 4 Julien Herran 2002-07-06 18:06:34 UTC
Do you get exactly the same errors, or has '/etc/sgml/' been
replaced by '/etc/sgml/' and '/usr/share/sgml/openjade-1.3/'
by '/usr/share/sgml/openjade-1.3.1/'?
Comment 5 Edward Muller 2002-07-06 18:16:43 UTC
errors are ...

jade:/etc/sgml/ cannot open
"/usr/share/sgml/openjade-1.3/catalog" (No such file or directory)
jade:/etc/sgml/ 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?
Comment 6 Edward Muller 2002-07-06 18:20:16 UTC
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?
Comment 7 Julien Herran 2002-07-06 18:24:47 UTC
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.
Comment 8 Edward Muller 2002-07-06 19:02:51 UTC
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.
Comment 9 Seemant Kulleen (RETIRED) gentoo-dev 2002-07-06 19:10:23 UTC
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. 
Comment 10 Julien Herran 2002-07-06 19:19:44 UTC
What kind of thing are you doing in the dev-perl ebuilds exactly ? :)
Comment 11 Seemant Kulleen (RETIRED) gentoo-dev 2002-07-06 19:42:11 UTC
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?
Comment 12 Seemant Kulleen (RETIRED) gentoo-dev 2002-07-06 19:42:50 UTC
btw, Ulkesh, keep in mind that I know _nothing_ about SGML and docbook etc
Comment 13 Julien Herran 2002-07-06 20:16:47 UTC
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.
Comment 14 Seemant Kulleen (RETIRED) gentoo-dev 2002-07-06 20:44:10 UTC

*** This bug has been marked as a duplicate of 4598 ***