[SOLVED] Failed to load external entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl

Hello. I'm barely hanging on here. I didn't sleep last night (I will tonight for sure!), but before I do, I need to ask this question:

How do I resolve the error found in the subject line of this post? I have encountered this error through updates of many sbopkg programs. I've found through my own researches tonight that I need to reinstall docbook-dtd, which is not even offered in sbopkg. Where do I go for help with issues with sbopkg?

Originally Posted by maschelsea Hello. I'm barely hanging on here. I didn't sleep last night (I will tonight for sure!), but before I do, I need to ask this question: How do I resolve the error found in the subject line of this post? I have encountered this error through updates of many sbopkg programs. I've found through my own researches tonight that I need to reinstall docbook-dtd, which is not even offered in sbopkg. Where do I go for help with issues with sbopkg?

Try reinstalling ap/linuxdoc-tools

Originally Posted by drmozes Try reinstalling ap/linuxdoc-tools

root@caitlyn:~# sbopkg -g linux-doctools
Searching for linux-doctools
sbopkg: No match for linux-doctools found.

Originally Posted by maschelsea root@caitlyn:~# sbopkg -g linux-doctools Searching for linux-doctools sbopkg: No match for linux-doctools found.

He meant off the installation media or your favorite Slackware server. linuxdoc-tools is an official package, not a 3rd-party on SBo. It is found under the ap/ series of packages. You can either download it manually or run slackpkg reinstall linuxdoc-tools if your slackpkg is set up.

Originally Posted by bassmadrigal linux-doctools is an official package

When you spell it as "linuxdoc-tools", yes it is <grin>.
But the OP should put the - in the right place then...

Originally Posted by ehartman When you spell it as "linuxdoc-tools", yes it is <grin>. But the OP should put the - in the right place then...

I should've looked closer... thanks (edited my original post). Either way, sbopkg won't find that package no matter where the hyphen is

It's fixed. Thank you for your excellent advice.