[ClusterLabs] pacemakerd --version display bug?

[Jan Pokorný]

On 23/02/16 22:07 +0000, Jeremy Matthews wrote:
> I recently installed pacemaker on a system and found it interesting
> that pacemaker -version and yum info pacemaker give different
> versions, 1.1.11 and 1.1.12, respectively:
> 
> 
> [root at g5se-f5c56a rc3.d]# pacemakerd --version
> Pacemaker 1.1.11
> Written by Andrew Beekhof
> 
> [root at g5se-f5c56a rc3.d]# yum info pacemaker
> [...]
> Version     : 1.1.12
> Release     : 8.el6_7.2
> [...]
> 
> They should be the same, right?  Maybe pacemaker -version should return 1.1.12?

Explanation is rather simple and boils down to upstream vs. downstream
versioning in the edge cases as this one -- maybe I could stop at
clarifying the RPM version you mention is based on Pacemaker-1.1.12-rc3,
but here we go a little bit deeper:

- upstream view: new version is not pronounced until real release is
  cut, i.e., what is tagged in due course is not a release candidate (rc);
  the procedure to get things ready for that includes bumping version in
  version.m4 source file, which is exactly what determines the response
  of --version for various Pacemaker binaries

- downstream view: pre-release of version X -> Version tag says X
  (info about this package being based on pre-release SHOULD be
  encoded in Release tag, but well, not always happens)


TL;DR this is an edge case involving an about-to-be-released version

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160225/652b58ac/attachment-0004.sig>