Do not hardcode a fixed release value but align it with the value used while tagging

[deneb-alpha]

Do not hardcode a fixed release value but align it with the value used while tagging.

Tested in:

• custom OBS project https://build.suse.de/project/show/home:deneb_alpha:branches:Devel:Galaxy:Manager:Head
• using this custom jenkins job https://ci.suse.de/view/Manager/view/Manager-Head/job/manager-Head-releng-2obs-temp-mlatini/

Now, if a source has been tagged using tito tag --use-release=0 the Release: will be set to 0, in case of sources still tagged with the default Release: 1 , the build script keep the 1 as a value.

a few examples from my branch:

• https://build.suse.de/package/show/home:deneb_alpha:branches:Devel:Galaxy:Manager:Head/billing-data-service

  • Release: 1 in spec file
  • - version 5.0.2-1 in .changes
  • same values in .obscpio

• https://build.suse.de/package/show/home:deneb_alpha:branches:Devel:Galaxy:Manager:Head/spacewalk-client-tools

• Release: 0 in spec file

• - version 5.0.4-0 in .changes

• same values in .obscpio

Same sources from Devel:Galaxy:Manager:Head:

• https://build.suse.de/package/show/Devel:Galaxy:Manager:Head/billing-data-service

  • Release: 1 in spec file
  • - version 5.0.2-1 in .changes
  • same values in .obscpio

• https://build.suse.de/package/show/Devel:Galaxy:Manager:Head/spacewalk-client-tools

  • Release: 1 in spec file
  • - version 5.0.4-0 in .changes
  • Release: 0 in .obscpio

for an untagged change, you can look at the current version of uyuni-releng-tools from this PR that is built in

• https://build.opensuse.org/package/show/home:deneb_alpha:branches:systemsmanagement:Uyuni:Master:Docker/uyuni-releng-tools
  • Release: 0 in spec file
  • untagged changes with the faketagger header as expected
  • Release: 0 in .obscpio

[cbosdo]

LGTM

[juliogonzalez]

LGTM

[deneb-alpha]

tested also with a push on https://build.opensuse.org/project/show/home:deneb_alpha:branches:systemsmanagement:Uyuni:Master. all looks fine