Bug 742097

Summary:	API compatibility no longer enforced
Product:	[Community] Publican	Reporter:	Ruediger Landmann <rlandman>
Component:	publican	Assignee:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.7	CC:	mhideo, rlandman+disabled, zdover
Target Milestone:	3.0
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	3.0.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-10-31 03:11:51 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 Ruediger Landmann 2011-09-29 03:06:00 UTC

Description of problem:
Publican 2.8 does not check for compatibility when it builds content packaged by older, incompatible versions

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

How reproducible:
100%

Steps to Reproduce:
1. Package a book using an obsolete (<2.5) version of Publican
2. Attempt to build the book from the package in an environment that has Publican 2.8 installed
  
Actual results:
Package gets built

Expected results:
Build should fail with a message that the package was created with an obsolete version of Publican

Comment 1 Jeff Fearn 🐞 2011-10-04 04:25:47 UTC

Re-added API check. Added extra check for post-commit DB hook, will not run check if DB update hooks are missing.

Committed revision 1903.

Comment 2 Jared MORGAN 2012-05-09 01:21:49 UTC

For verification, can we get older versions of publican from brew?

Would the verification steps be:

Prerequisites:

* ensure brew has publican v2.8 installed (which it should by default, yes?)

1. yum downgrade publican (to revert to non-testing version). 
2. Uninstall publican. 
3. Install old publican package. 
4. Test fix.