Bug 751782

Summary:	Provide Topic Tool build for F16
Product:	[Other] Topic Tool	Reporter:	Stephen Gordon <sgordon>
Component:	cli-Topic_Tool	Assignee:	Stephen Gordon <sgordon>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.0.x	CC:	topic-tool-list
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-07 16:22:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Stephen Gordon 2011-11-07 14:54:26 UTC

Description of problem:

F16 is going gold (yay!). Need to provide a build of 0.0.8 for F16, this should be pretty straight forward - just need to check none of the apache/jakarta commons dependencies have changed names.

Spec file change is likely to result in generation of 0.0.8-2, but given no functional change will leave other distro builds at 0.0.8-1 for now.

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

0.0.8

Comment 1 Stephen Gordon 2011-11-07 16:22:49 UTC

No changes to the spec file required, looks like I had pre-emptively guessed that the F16 names would be unchanged which is indeed the case.

As a result have simply rebuilt from the 0.0.8-0 tag in SVN and created the repo structure for the resulting RPM.