The test in configureRelease if the package is already in the repository has no effect due to wrong package version

[zenker]

I just realized that the comparison here

DebianPackagingScripts/configureRelease

Line 568 in a2cd9c3

if(currentVersion == config["package-version"]):

does not work. E.g. current version is 01.10focal1.03-0 but config["package-version"] is 01.10focal1.03. So the appended -0 from the version number in the repository is not reflected in config["package-version"].

I don't now were that -0 is added, but because of that issue the test will always fail. Potentially, this allows to publish packages that already exists in the repository.

[mhier]

It seems the -0 is hardcoded somewhere (probably through the changelog -> debchange call?), so we can just add it on the one side of the test, or strip it on the other side.

I think I prefer stripping, since it has the advantage of breaking "nicer" in case we no longer hardcode the number in future.