Bug 1037037 - Empty conf files cause exception
Summary: Empty conf files cause exception
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 4.1
Assignee: Jeff Fearn 🐞
QA Contact: Ruediger Landmann
URL:
Whiteboard:
: 1061434 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-03 02:58 UTC by Jeff Fearn 🐞
Modified: 2014-05-05 06:03 UTC (History)
3 users (show)

Fixed In Version: 4.1.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-05 06:03:27 UTC
Embargoed:

Attachments (Terms of Use)

Description Jeff Fearn 🐞 2013-12-03 02:58:55 UTC 
Description of problem:
If you have any config file that is empty, or only comments, then publican dies at the attempt to load it. Publican also emits a default message and does not pass on the config modules error string.

1: If possible empty configs should be loaded without issue.

2: Any time that a config files fails to load the config modules error message should be passed on to the user.
Comment 2 Jeff Fearn 🐞 2014-02-23 23:20:46 UTC 
*** Bug 1061434 has been marked as a duplicate of this bug. ***
Comment 3 Jeff Fearn 🐞 2014-03-20 01:57:25 UTC 
I limited this change to only affect the brand default.cfg and overrides.cfg, all other cfg files that exist should not be empty.

To ssh://git.fedorahosted.org/git/publican.git
   1a4f78b..d6b2ed6  devel -> devel
Comment 4 Jeff Fearn 🐞 2014-05-05 06:03:27 UTC 
A fix for this shipped in Publican 4.1.0.
Note You need to log in before you can comment on or make changes to this bug.