Bug 1105090 - unrtf templates not found
Summary: unrtf templates not found
Keywords:
Status: CLOSED DUPLICATE of bug 1060513
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: unrtf
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ken Dreyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-05 11:16 UTC by Arne de Bruijn
Modified: 2014-06-07 01:50 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-07 01:50:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Arne de Bruijn 2014-06-05 11:16:03 UTC
Description of problem:


Version-Release number of selected component (if applicable):
unrtf-0.21.5-1.el6


How reproducible:
echo '{}'|unrtf

Actual results (error message):
failed to find html.conf in search path dirs

Expected results:
<!DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN>
...

Additional info:
unrtf looks for html.conf in /usr/share/unrtf, but the package places the file in /etc/unrtf.
unrtf used to use a hardcoded conf-file path which was replaced in the .spec file. But the latest version has a macro CONFIG_DIR defined to PKGDATADIR.
Since the conf files are more static template files than user configurable files PKGDATADIR seems right.

Comment 1 Ken Dreyer 2014-06-07 01:50:57 UTC
Hi Arne, thanks for the bug report. As it turns out this bug looks very similar to 1060513 , "conf files are not found". If you don't mind I'm going to close this one as a duplicate of that one. 

As described in the other bug, there is a newer unrtf package in epel-testing, and when that update reaches the end of its two week testing period, I can push it to epel's stable repo.

If you get a chance to check out the package in epel-testing, I would greatly welcome your feedback. Feel free to comment in Bodhi or on that original bug in Bugzilla.

*** This bug has been marked as a duplicate of bug 1060513 ***


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