Bug 806131

Summary:	push updates wrong local contentspec
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	CSProcessor	Assignee:	Lee Newson <lnewson>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	jwulf, lcarlon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	0.22.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-07 01:30:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joshua Wulf 2012-03-23 01:34:08 UTC

cspclient-0.22.3-1.noarch

When I execute csprocessor push my local Red_Hat_Engineers_Guide_to_Zanata-post.contentspec is not updated.

Actual behaviour:

Another directory is created inside my project directory, with the same name as my project-  "Red_Hat_Engineers_Guide_to_Zanata" - and the server's latest content spec is downloaded as Red_Hat_Engineers_Guide_to_Zanata-post.txt

Expected behaviour:

The local Red_Hat_Engineers_Guide_to_Zanata-post.contentspec in the current directory is overwritten with the latest server-side content spec

Comment 1 Lee Newson 2012-03-23 02:21:11 UTC

Fixed in 0.22.4

This is from another bug that Josh notified me about on irc but appears I missed for the push command.

Cause:
The program assumed that the root directory would always be set. This was causing the root directory to be set to the CWD and therefore populating the new project files in the CWD.

Consequence:
The program produced unexpected results and was creating directories where it shouldn't be.

Fix:
If no root directory is specified it will use the CWD to save items. If a root directory is specified then it will use that with the escaped title appened to save items.

Comment 2 Lee Newson 2013-06-07 01:30:20 UTC

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.