Bug 1395988

Summary: Non-compliant package versioning
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: krb5Assignee: Robbie Harwood <rharwood>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: abokovoy, j, nalin, npmccallum, rharwood
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-17 14:00:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Adam Williamson 2016-11-17 07:33:16 UTC 
I noticed current Rawhide krb5-libs package is versioned as follows:

krb5-libs-1.15-2.fc26.beta1.0.x86_64

this is not at all compliant with the versioning policy:

https://fedoraproject.org/wiki/Packaging:Versioning

It has some examples for pre-releases:

https://fedoraproject.org/wiki/Packaging:Versioning#Examples

basically, this should be something like:

krb5-libs-1.15-0.2.beta1.fc26

you'd bump the '2' digit each time you do a pre-release build, regardless of whether the 'beta1' changes or not. Then when the final 1.15 release comes out, you'd make it:

krb5-libs-1.15-1.fc26

Unfortunately you can't fix this now for the 1.15 series without using an epoch, but I figured it's worth reporting to avoid this happening in future.
Comment 1 Robbie Harwood 2016-11-17 14:00:57 UTC 
Alright, as far as I can tell this is the way we've always done it.  I can't immediately figure out why that is, so I've put comments in the git tree and we'll see what (if anything) breaks for 1.16.