Skip to content

eCAL internal and python packaging produce different version numbers #2588

Description

@KerstinKeller

Problem Description

Currently, eCAL internally calculates a version number using git describe, and python packaging also computes a version number for it.
However, these version numbers don't match under certain conditions. However they are compared in Python unit tests, which leads to failing unit tests.

We have to adapt one or the other to achieve matching version numbers.
(only true for commits which are not a clean tag).

How to reproduce

Run eCAL Python unittests e.g. on support/v6.1

Unit test failure output

         assert version.major == ecal_package_version.major
          assert version.minor == ecal_package_version.minor
  >       assert version.patch == ecal_package_version.micro
  E       AssertionError: assert 0 == 1
  E        +  where 0 = <Version major=6, minor=1, patch=0>.patch
  E        +  and   1 = <Version('6.1.1.dev14+g9217d1f06')>.micro

Metadata

Metadata

Assignees

No one assigned

    Labels

    beginnerbugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions