OBS nightly package upgrading breaks if commit did not change
Nightly packages are built every night, even if their source did not change. All nightly packages depend on a "conflict package" osmocom-nightly with the build date set as version.
However, if the source does not change, the resulting version of a package does not change either.
If the package is already installed and the user tries to upgrade it, the package manager assumes that the installed package does not need to be upgraded as the version is the same.
This results in breakage if other packages do have different versions, and want to pull in a new version of osmocom-nightly, but at least one package has the same version and still depends on the old osmocom-nightly.
Workaround: remove the packages and install them again.
Let's fix this by increasing the debian_revision:
debian policy manual [epoch:]upstream_version[-debian_revision]
so we'd use the -debian_revision
so the upstream versions stays the same but something in the package has changed