Bug 689347 - Even when building a <set> works ... brewing it doesn't.
Summary: Even when building a <set> works ... brewing it doesn't.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Ruediger Landmann
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-21 07:13 UTC by Rebecca Newton
Modified: 2011-07-26 00:42 UTC (History)
2 users (show)

Fixed In Version: 2.6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-26 00:42:47 UTC
Embargoed:


Attachments (Terms of Use)

Description Rebecca Newton 2011-03-21 07:13:36 UTC
Description of problem: Even when a <set> builds successfully locally, it doesn't when attempting to brew by running:

publican package --brew --lang en-US --wait

This happens!

Running clean process to ensure stale content is not bundled in packages.
Clean: Removing tmp and publish directories.
Use of uninitialized value in lc at /usr/share/perl5/Publican/Builder.pm line 2167, <FH> line 15.
Config parameter 'scm' not found; treating set as standalone.
'books' is a required configuration parameter for a remote set at /usr/bin/publican line 765

Version-Release number of selected component (if applicable):


How reproducible:
Create a standalone set and try to brew or scratch brew. Here is my svn repository for the WFK Seam Developer Guide:

https://svn.devel.redhat.com/repos/ecs/JBoss_Web_Framework_Kit/trunk/1.2/



Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jeff Fearn 🐞 2011-04-06 10:15:02 UTC
Added an extra check to package to check if a set is remote or not.

Fixed in revision 1743.

Comment 2 Jeff Fearn 🐞 2011-07-05 11:37:55 UTC
Back ported to branches/publican-2x

Committed revision 1804.

Comment 3 Rebecca Newton 2011-07-13 04:55:04 UTC
Verified! My set brews for the first time, huzzah!


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