knome wrote:As a matter of interest, how did you figure that out?
For me, it all starts with the sourcery (or slapt-src ) build failure log output. I found that for the large majority of these build failures the problem can be found in the line or two just before the first make[ ]error line. I first try searching slapt-get and slapt-src using key words in the line in addition to googling the complete line or part of it. In this case the line of interest is:
Code: Select all
xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl
Turns out that the keyword here is docbooks. Doing a slapt-get --search docbook you get the following output;
Code: Select all
root[rich]# slapt-get --se docbook
abiword-2.8.6-x86_64-3gv [inst=no]: abiword (word processing for everyone)
linuxdoc-tools-0.9.67-x86_64-2 [inst=yes]: linuxdoc-tools (utilities for working with DocBook and SGML)
txt2tags-2.6-noarch-1 [inst=no]: txt2tags 2.6 (Text formatting tool)
xorg-docs-1.7-noarch-1 [inst=no]: xorg-docs (documentation for X11)
I actually ran into this build issue before with pygtksourceview and once I saw linuxdoc-tools, I knew that it was the missing build dependency. If i hadn't know I would have tried installing these one at a time (I would have skipped both abiword and xorg-docs) and see which one allowed pygtksourceview to successfully build. Bottom line for me is that it usually involves googling and trial and error installs, but as mimosa said once you get some experience building packages, you usually get to the correct answer a lot faster.
Also, before posting any response, i try to confirm that the solution that I am suggesting works. In this case I try building pygtksourceview and confirmed that the build failed in the same way that it did for globetrotterdk and then after installing linuxdoc-tools confirmed that pygtksourceview build successfully.
“Don’t you see that the whole aim of Newspeak is to narrow the range of thought?"