Bug 191306 - Kde Help Center can't build an index
Summary: Kde Help Center can't build an index
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-10 17:26 UTC by Penelope Fudd
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-05-19 18:25:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Penelope Fudd 2006-05-10 17:26:06 UTC
Description of problem:
In Konsole, I clicked on help/Konsole Handbook, and the KDE help center popped
up.  Building a search index seemed to be the thing to do, so I checked the box
for unix man pages, and clicked on 'Build search index'.  On the next screen I
checked 'Application manuals' and clicked on 'Build index'.

The process finished amazingly fast, so I was suspicious that it didn't do
anything at all.  That seems to be the case; after clicking on 'Details' the
dialog box ends with 'htdig failed'.  It appears that htdig isn't installed.

Version-Release number of selected component (if applicable):
kdebase-3.5.2-0.4.fc5

How reproducible:
Every time.

Steps to Reproduce:
1. See above
2.
3.
  
Actual results:
INDEXDIR: /home/croot/.kde/share/apps/khelpcenter/index/
FINDCMD: find /usr/share/doc/HTML/en/ -name index.docbook
Creating index for 'kde_application_manuals'
htdig failed

Expected results:


Additional info:

Comment 1 Penelope Fudd 2006-05-10 17:28:54 UTC
I've installed htdig ('yum install htdig'), and the problem goes away.

The rpm for kdebase either needs to have a dependency for htdig added, or it
needs to have a workaround if htdig is not installed.

Comment 2 Than Ngo 2006-05-19 18:25:47 UTC
yes it seems htdig is needed here. I have added requires on htdig in next
kdebase rebuild. It will be available in FC5-update soon. Many thanks for your
report.


Note You need to log in before you can comment on or make changes to this bug.