Red Hat Bugzilla – Bug 804487
Revision History invalid with Publican 3
Last modified: 2014-10-19 19:00:24 EDT
The Revision History generated by the Content Spec processor is invalid in Publican.
[jwulf@radhe Messaging_Installation_and_Deployment_Guide]$ csprocessor assemble
CSProcessor client version: 0.22.3
Loading configuration from /home/jwulf/.config/csprocessor.ini
Connecting to Skynet server: http://skynet.usersys.redhat.com:8080/TopicIndex/
Starting to validate...
Starting to build...
Content Specification successfully built with 0 Errors and 2 Warnings
Output saved to: /home/jwulf/scratch/Messaging_Installation_and_Deployment_Guide/assembly/Messaging_Installation_and_Deployment_Guide-publican.zip
Starting to assemble...
Content Specification build unzipped to /home/jwulf/scratch/Messaging_Installation_and_Deployment_Guide/assembly/publican
Starting the publican build...
) does not match the required format of '^([0-9.]*)-([0-9.]*)$/' at /usr/bin/publican line 632
I'm unable to reproduce this, so what version of publican are you using? By the looks of the regex expression it's matching it should be fine (though the "$/'" is sorta worrying). I should also note that that part hasn't changed since the program was created.
Publican 3 from source.
A new book created with Publican 3 has the rev history formatted like this:
That doesn't matter, 0-0 will still work. The problem is that the older publican versions, used older PERL libraries which trimmed white space and newlines. It appears that the latest versions don't do this which is what is causing the problem. I still need to look into it more though.
Fixed in 0.22.4
I've made the <revnumber> tag be processed as an inline element. If anyothers pop up let me know. Though this is more of a publican issue in my opinion, as it should be able to handle white-space rather then all users having to enter <revnumber>0-0</revnumber> with no spaces.
Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.