Bug 921333 - web-spec.xml missing whitespace - results in packages not building
Summary: web-spec.xml missing whitespace - results in packages not building
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: publican
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Ruediger Landmann
QA Contact: Andrew Ross
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-14 02:57 UTC by Andrew Ross
Modified: 2013-10-20 22:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-17 00:37:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
updated web-spec (8.50 KB, application/xslt+xml)
2013-03-14 02:57 UTC, Andrew Ross
no flags Details
web-home-spec.xsl patch (734 bytes, patch)
2013-03-14 03:13 UTC, Andrew Ross
no flags Details | Diff

Description Andrew Ross 2013-03-14 02:57:49 UTC
Created attachment 709854 [details]
updated web-spec

Description of problem: web-spec.xml is missing whitespace in the BuildRequires and %post sections. This causes issues when using a brand other than common.

The missing \n in BuildRequires prevents packages from being built.
The missing space chars in %post prevent web_product_label from being overridden in publican.cfg 


Version-Release number of selected component (if applicable):
publican-3.1.3-1.fc18.noarch

How reproducible:


Steps to Reproduce:
1. Create a book with a different brand (eg. brand: RedHat)
2. Build an rpm (publican package --binary)
3. Install to a publican website
  
Actual results: Package creation fails.


Expected results:


Additional info: I have attached a version of the web-spec.xsl that works. This web-spec includes the changes made by lnewson to fix the build issue (BuildRequires).

Comment 1 Andrew Ross 2013-03-14 03:13:08 UTC
Created attachment 709857 [details]
web-home-spec.xsl patch

Comment 2 Ruediger Landmann 2013-04-17 00:37:09 UTC
Fixed in 3.1.5-1, now in testing for F17 and F18


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