Bug 1986522

rpmdev-bumpspec messes up with nss/nspr. nss/nspr uses two globals for the version number. rpmdev-bumpspec modifies the Release field directly and adds the .1 after the %{?dist} variable.

Consider defining %baserelease macro (rpmdev-bumpspec will bump the one if it sees it) and using it to calculate the values of %nspr_release and %nss_release.

E.g.:
%global baserelease 2
%global nspr_release %{lua:print(rpm.expand('%baserelease') + 0)}
%global nss_release %{lua:print(rpm.expand('%baserelease') + 1)}

Or even better, without Lua, if you only need to support RPM 4.16+:

%global baserelease 2
%global nspr_release %[%baserelease+0]
%global nss_release %[%baserelease+1]

Thanks,
I only need rpm support in Fedora and RHEL 9, so i suspect 4.16+ is fine (rhel 8 still builds nss/nspr separately).

The base release offset isn't always a fixed number. If I rebase nss, but not nspr then nspr increments and nss goes to 1, however if rpmdev-bumpspec understands it then it's worth changing and doing the math myself.

I meant that rpmdev-bumpspec would always bump %baserelease and never break the package and when you rebase nss, but not nspr, then you need to adjust the +Ns manually.

Thanks Miro, Once this build is complete I'll add the baserelease version.

Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 35.

Thanks for taking care of it!