Description of problem: gridsite package also builds gridsite1.7-compat package which has different version. Because there is two defintions of %{version} dependencies are wrong. Two possible ways to fix the issue are: Make sure %{version} macro is not used anywhere in the spec, you need to use %{compatver} and or %{normalver} in every case where %{version}. Or better yet: Create new girdsite1.7-compat package which provides old library version. Current problems are for example with provides and dependencies where: rpm -q --provides -p gridsite-clients-2.0.4-1.el6.i686.rpm gridsite-commands = 1.7.25-1 gridsite-clients = 2.0.4-1.el6 gridsite-clients(x86-32) = 2.0.4-1.el6 Note also that gridsite1.7-compat has: Release: %{compatrel} - %{?dist} is missing... you can see results of that on that previous provides where dist tag is missing...
If you decide to continue having two library versions in same package I'd also note that one Release: instance is enough - compat doesn't need it's own release number - having two release number makes this package even more error prone - you might end up building same release version of gridsite1.7-compat twice if you forget to update the release tag of sub-pacakge.
Created attachment 800890 [details] Proposed patch for packaging issues
Hi, So I already did something before seeing this bug to correct the issue. Which corrects the issues. Re: > gridsite1.7-compat package which has different version. yes this is intentional. >you might end up building same release version of gridsite1.7-compat twice if you forget to update the release tag of sub-pacakge. koji does make this impossible as it won't let you repeat a build result. As you say you have bump both release numbers each time. New packages now in testing. Will leave this open in case of further comment.
(In reply to Steve Traylen from comment #3) > > gridsite1.7-compat package which has different version. > > yes this is intentional. Of course this is. > >you might end up building same release version of gridsite1.7-compat twice if you forget to update the release tag of sub-pacakge. > > koji does make this impossible as it won't let you repeat a build > result. As you say you have bump both release numbers > each time. I know that. But having two Release definitions is totally unnecessary and makes spec over-compliated and more error prone. > New packages now in testing. Will leave this open in case of further > comment. Thank you.
Indeed next time I touch the packages I'll merge the normalrel and compatrel into one one variable, indeed there is no reason why these would ever need to be increased differently.
gridsite-2.2.0-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/gridsite-2.2.0-1.el6
Package gridsite-2.2.0-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing gridsite-2.2.0-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-12417/gridsite-2.2.0-1.el6 then log in and leave karma (feedback).
gridsite-2.2.0-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.