| Summary: | the emerge -e system stop by docbook-sgml-utils | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | klaus henske <khenskelinux> |
| Component: | New packages | Assignee: | Text-Markup Team (OBSOLETE) <text-markup+disabled> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | CC: | darren, jon, ronny |
| Priority: | Highest | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge output from emerge ~docbook-sgml-dtd-3.1 | ||
|
Description
klaus henske
2005-07-13 08:22:43 UTC
the host in the field rsync-server is a host from me. I use him as rsync-server for my servers in schools. This ist a host on a dsl-flat with dyndns-hostname. Can act this server as rsync-mirror? Please file those long outputs as attachments. Also, the problem seems to be with some of docbook-sgml-utils dependencies. Did docbook-sgml-dtd-3.1 and docbook-dsssl-stylesheets get emerged before docbook-sgml-utils? Please try installing these manually: emerge docbook-dsssl-stylesheets emerge ~docbook-sgml-dtd-3.1 If something goes wrong with any of those, please attach here the relevant output. Thanks. Sorry, the package docbook-dsssl-stylesheets and ~docbook-sgml-dtd-3.1 are on the system and an emerge of this packages don't remove the error. What are the contents of the file /etc/sgml/catalog in your system? Also, just to check, please attach the complete output from "emerge ~docbook-sgml-dtd-3.1" anyway. Thanks. Created attachment 63398 [details]
emerge output from emerge ~docbook-sgml-dtd-3.1
I think, that the problem ist in this lines from
/usr/portage/eclass/sgml-catalog.eclass:
/usr/portage/eclass/sgml-catalog.eclass: line 36: toinstall: bad array
subscript
/usr/portage/eclass/sgml-catalog.eclass: line 37: toinstall: bad array
subscript
/usr/portage/eclass/sgml-catalog.eclass: line 59: toinstall: bad array
subscript
/usr/portage/eclass/sgml-catalog.eclass: line 60: toinstall: bad array
subscript
i hope, that was. What is to do, to correct this error?
I can confirm this same error when building a livecd via catalyst. I've noticed it the past couple days (with a new portage snapshot each day) and haven't been able to track it down. i can confirm this error on the amd64 version... However, I didn't get the error on emerge -e system, but when emerging gnome. can confirm always repeatable on my x86 (normal update, not system). No other
deps waiting - emerged them all manually prior to retrying this one.
Last bit of output shows:
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: error while loading shared libraries: libosp.so.3: cannot open shared
object file: No such file or directory
make[2]: *** [api.html] Error 127
make[2]: Leaving directory
`/tmp/portage/docbook-sgml-utils-0.6.14/work/docbook-utils-0.6.14/doc/HTML'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/tmp/portage/docbook-sgml-utils-0.6.14/work/docbook-utils-0.6.14/doc'
make: *** [all-recursive] Error 1
so did following:
garbo ~ # locate libosp.so
/usr/lib/libosp.so
/usr/lib/libosp.so.4.0.0
/usr/lib/libosp.so.4
garbo ~ # cd /lib
garbo lib # ls -al libosp.so*
lrwxrwxrwx 1 root root 15 Mar 15 00:47 libosp.so -> libosp.so.4.0.0
lrwxrwxrwx 1 root root 15 Mar 15 00:47 libosp.so.4 -> libosp.so.4.0.0
-rwxr-xr-x 1 root root 1968608 Mar 15 00:47 libosp.so.4.0.0
garbo lib # ln -s libosp.so.4.0.0 libosp.so.3
.. then re-emerged. This just caused jade to hang for about 10 mins (CPU at
100%) before I killed it.
Maybe an older version of opensp is required??
garbo lib # qpkg -f /usr/lib/libosp.so.4.0.0
app-text/opensp *
Regards,
(Regarding comment #5) Then this certainly is the same issue as bug #98680, that's what I wanted to know from the start. This is not a problem directly related to docbook-sgml-utils, but apparently something's failing in the eclass. Darren (comment #8), The problem you're seeing is different in nature. You should probably re-emerge openjade. *** This bug has been marked as a duplicate of 98680 *** |
