Bug 92143

Summary:	SA explicit epoch in dep for promotion safety
Product:	[Retired] Red Hat Raw Hide	Reporter:	Warren Togami <wtogami>
Component:	spamassassin	Assignee:	Chip Turner <cturner>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-11-28 07:08:28 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 Warren Togami 2003-06-03 08:48:27 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030509

Description of problem:
Good work with spamassassin-2.55-1.  Only one very minor comment.

The spec has "BuildRequires: perl >= 2:5.8.0" with the explicit epoch:version
which is good, however earlier in the spec you have "Requires: perl >= 5.004"
which would be the actual cause of a problem should perl epoch ever increment. 
Please consider "Requires: perl >= 2:5.004".

If you are not familiar with the epoch promotion issue, read the extremely long
recent threads on rpm-list where people are very upset.  Use "rpm -Vav
--nofiles" to see the many many instances in RH where deps-with-versions are
missing an epoch... all potential epoch promotion clashes in for rpmvercmp in
the future.

Yeah, this issue probably never would be triggered since Epoch is very unlikely
to ever increment for perl, but explicitness for safety should not hurt.

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

Comment 1 Chip Turner 2003-06-03 13:38:39 UTC

fixed in cvs, should be in the next build