| Summary: | install script to register docbook 4.1.2 catalogs segfaults repeatedly | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | David Lehr <naitram> |
| Component: | Current packages | Assignee: | Matthew Turk (RETIRED) <satai> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | obz |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | strace of the docbook catalog register script. | ||
|
Description
David Lehr
2003-08-09 05:52:53 UTC
*** Bug 26263 has been marked as a duplicate of this bug. *** Created attachment 15830 [details]
strace of the docbook catalog register script.
So, being the highly intelligent individual that i am, i manage to submit the bug report twice, and unfortunately the report that was a little more complete was the one that was removed. So... From a 1.4 athlon-xp release disc, started with stage2, emerge bitchx brought about gnome, which brought scrollkeeper. scrollkeeper errored with a message that it could not find docbook dtd catalogs but to obtain information about this problem from: http://scrollkeeper.sourceforge.net/docbook.shtml . That page offers a script (http://scrollkeeper.sourceforge.net/data/docbookx412.tgz) to fix the issue, and when trying to run the script, it segfaults multiple times. Output from running that script will be posted shortly, as soon as i can access the system. My apologies for being mildly inept and double posting the bug. okay, scrollkeeper depends on docbook-xml-dtd 4.1.2, do you have it installed ? could you try sync'ing and emerging docbook-xml-dtd-4.1.2-r4 and report back on the success ? thanks Unfortunately I don't have that install available anymore. Fortunately the problem hasn't come up in any installs since. I spoke to one of the guys at the Gentoo boot at the linuxworld expo in SF, and he guessed that it had to do with the use flags being changed mid-way through the install (i didn't realize that they were still commented out) but asked that i submit a bug report. Since that install is no longer around, and now i can't duplicate the problem, i'm guessing this should be closed off or marked as stale or something to the effect. yep, thanks very much for reporting back. |