Project

General

Profile

Bug #4925

version_compare_numeric does not work for 2.2.9 to 2.2.10

Added by Phillip Davis over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Upgrade
Target version:
Start date:
08/08/2015
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

version_compare_numeric correctly compares 2.2.8 to 2.2.9 and thinks 2.2.9 is an upgrade - good.
But comparing 2.2.9 to 2.2.10 it thinks 2.2.10 is an earlier version than 2.2.9 - not good.
The same problem exists for any last number position in the dot-separated list - e.g. 3.9 to 3.10 will not be seen as an upgrade.

I would like to use this an related functions to compare package versions also. Package versions often transition from (0.9 to 0.10) (1.1.9 to 1.1.10) (1.1.19 to 1.1.20). So it would be nice to fix the function.

History

#2 Updated by Chris Buechler about 4 years ago

  • Status changed from New to Confirmed

#4 Updated by Chris Buechler about 4 years ago

  • Status changed from Confirmed to Resolved
  • Target version set to 2.2.5
  • Affected Version set to All

Thanks Phil.

Also available in: Atom PDF