Bug 467147 - Insufficient error reporting when no revision history is present.
Summary: Insufficient error reporting when no revision history is present.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 2.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Content Services Development
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-15 23:31 UTC by Ryan Lerch
Modified: 2010-11-24 03:59 UTC (History)
2 users (show)

Fixed In Version: 0.38
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-16 02:47:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Ryan Lerch 2008-10-15 23:31:28 UTC
Description of problem:
when building the web-srpm (i tested with make web-brew-scratch-en-US) and no Revision History is present in the book / article, publican's error reporting is not very useful:

START: web-srpm-en-US: Thu Oct 16 07:16:41 EST 2008
 I/O error : Is a directory
 tmp/en-US/xml/:1: parser error : Document is empty
 ^
 tmp/en-US/xml/:1: parser error : Start tag expected, '<' not found
 ^
 I/O error : Is a directory
 unable to parse tmp/en-US/xml/
 make: *** [web-srpm-en-US] Error 6

Comment 1 Jeff Fearn 🐞 2008-10-16 02:47:18 UTC
Added check for valid revision history file when building rpms.

Added error message:

*ERROR: No revhistory found*
You need a correctly formatted Revision History to build RPMS
make: *** [web-srpm-en-US] Error 5

Comment 2 Ryan Lerch 2008-10-16 03:32:24 UTC
thanks for the fast turnaround on this one jeff!
:)

Comment 3 Fedora Update System 2008-10-16 22:44:06 UTC
publican-0.38-0.fc9,perl-XML-TreeBuilder-3.09-11.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/publican-0.38-0.fc9,perl-XML-TreeBuilder-3.09-11.fc9

Comment 4 Fedora Update System 2008-11-07 02:55:25 UTC
publican-0.38-0.fc9, perl-XML-TreeBuilder-3.09-11.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.


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