[pve-devel] applied: [PATCH] pvecfg: adapt version and release semantic

[Thomas Lamprecht]

On 5/27/19 7:02 AM, Thomas Lamprecht wrote:
> Wit commit bcef9bde68a920a4d204beb8ec1d5f334f7fbb78 we switched over
> to using the dpkg-dev provided helpers to set package version,
> architecture and such in the buildsystem.
> 
> But unlike other repositories we used the version also for giving it
> back over the API through the during build generated PVE::pvecfg
> module, which wasn't fully updated to the new style.
> 
> This patch does that, and also cleans up semantics a bit, the
> following two changed:
> 
> release is now the Debian release, instead of the "package release"

s/Debian release/PVE release/

> (i.e., the -X part of a full package version).
> version is now simply the full (pve-manager) version, e.g., 6.0-1 or
> the currently for testing used 6.0-0+1
> 
> This allows to do everything we used this information for even in a
> slightly easier way (no  string concat needed anymore), and fits also
> with the terminology we often used in our public channels (mailing
> lists, forum, website)
> 
> Remove some cruft as we touch things.
> 
> Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
> ---
> 
> While the API return values stays the same it's not the same values encoded
> there, so this can be considered as rather unspectacular breaking change.
> 
>  Makefile                  |  5 +++--
>  PVE/API2/Nodes.pm         | 15 ++++++++++++---
>  PVE/APLInfo.pm            |  4 ++--
>  PVE/Makefile              |  2 +-
>  PVE/Report.pm             |  2 +-
>  PVE/Service/pveproxy.pm   |  5 ++---
>  PVE/pvecfg.pm.in          | 16 +++++++---------
>  www/manager6/Workspace.js |  2 +-
>  8 files changed, 29 insertions(+), 22 deletions(-)
>