> Since you know much more about the docbook system than I do, > can you take > a look at this build failure of tdevelop? > http://quickbuild.pearsoncomputing.net:58080/2587282/buildlog_ubuntu-lucid-i386.tdevelop-trinity_4%3A14.0.0-0ubuntu4%2Br101%2Bpr8~lucid_FAILEDTOBUILD.txt.gz > > I suspect it is related to the changes that you pushed > earlier. General discussion for all: :) The errors indicates something fishy with finding various entities. Many of the entities used in the docbook files are found in the general.entities file. In the source tree the file is located at: tdelibs/kdoctools/customization/entities/general.entities When installed as a package the file is located at: $PREFIX/share/apps/ksgmltools2/customization/entities/general.entities The latter location is the important one when building packages. In that file should be the entities mentioned in the build log: &tde;, &kcontrolcenter;, etc. They do exist because I merged that patch and the file is fine here in my local repository. So the next thing to look at in tdevelop/doc/tdevelop/index.docbook. Look at the top of the file to notice a DOCTYPE declaration. The DTD file referenced in that DOCTYPE declaration, dtd/kdex.dtd, contains the reference to general.entities. In the problematic file: <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [ But should be this: <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [ There are four tdevelop docbook files that need to be patched: tdevelop/doc/tdevelop/index.docbook tdevelop/doc/kdearch/index.docbook tdevelop/doc/kde_app_devel/index.docbook tdevelop/parts/appwizard/common/kde-index.docbook Root cause analysis: I was sure I had updated all main package docbook DOCTYPE declarations, but of course, perhaps I missed some. Looking at the Commit Patches web page, I don't see tdevelop in the list. Short-term: patch the affected files with the correct DOCTYPE declaration and the files should build. Odd that I built the package here only a few days ago. I'll push a patch tonight. P.S. There are many docbook files in main/applications that I have not yet pushed patches because I don't build those packages. I have the patches in my queue but I need to actually build the packages locally to ensure the patches are sound before I push. Reason: I found one package where the patch caused the build to fail (kipi-plugins), which is why I don't push the whole bundle. I need to figure why that happens and ensure that does not happen with the other main/applications packages. My to-do list contains building and testing those packages. Darrell