Bug 176038 - No dict.conf defined
Summary: No dict.conf defined
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: dictd
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-18 01:20 UTC by Paul Dickson
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-12-19 13:06:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Paul Dickson 2005-12-18 01:20:40 UTC
Description of problem:
The dict program complains "'dict.conf' doesn't specify any dict server".

Reverting to dictd-1.9.7-8.i386.rpm resolves the problem.

Version-Release number of selected component (if applicable):
dictd-1.9.15-3

How reproducible:
Always

Steps to Reproduce:
1. dict adequate
2.
3.
  
Actual results:
$ dict adequate
'dict.conf' doesn't specify any dict server


Expected results:
$ dict adequate
4 definitions found

From The Collaborative International Dictionary of English v.0.48 [gcide]:

  Adequate \Ad"e*quate\, a. [L. adaequatus, p. p. of adaequare to
     make equal to; ad + aequare to make equal, aequus equal. See
     {Equal}.]

[...etc]

Additional info:
Might need to include a default /etc/dict.conf for newer versions.

Comment 1 Karsten Hopp 2005-12-19 13:06:13 UTC
We had a default /etc/dict.conf for some time, but we've never shipped any
dictionaries. This resulted in different errors. Therefore I've decided to leave
it up to the packagers of the dictionaries to polulate /etc/dict.conf.
See bug #135920 

Comment 2 Nalin Dahyabhai 2005-12-19 22:19:12 UTC
The client's previous default behavior was to consult "dict.org" and
"alt0.dict.org" if no server was explicitly specified on its command line.
I don't know why this was changed upstream, but the previous default can be
restored by passing "--enable-dictorg" to the configure script.

Comment 3 Karsten Hopp 2005-12-20 10:33:02 UTC
comment #2: you're right. I didn't notice this upstream change. dictd-1.9.15-4
will have this fix.


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