Bug 176038
Summary: | No dict.conf defined | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul Dickson <paul> |
Component: | dictd | Assignee: | Karsten Hopp <karsten> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | nalin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-12-19 13:06:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Paul Dickson
2005-12-18 01:20:40 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 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 #2: you're right. I didn't notice this upstream change. dictd-1.9.15-4 will have this fix. |