http://bugzilla.opensuse.org/show_bug.cgi?id=1179521 http://bugzilla.opensuse.org/show_bug.cgi?id=1179521#c13 Benjamin Greiner <code@bnavigator.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |badshah400@gmail.com, | |code@bnavigator.de See Also| |https://bugzilla.opensuse.o | |rg/show_bug.cgi?id=1196682 Resolution|--- |FIXED --- Comment #13 from Benjamin Greiner <code@bnavigator.de> --- (In reply to Stefan Br�ns from comment #12)
rpm -E 'requires_eq libhdf5' expands to "%nil". It has to include soversion, i.e. libhdf5-103 (currently). Obviously, this does not scale ...
But rpm -E '%requires_eq hdf5' expands to 'Requires: hdf5 = 1.10.8'. The macro requires a proper package name. It does not work with symbolic rpm capabilities. The hdf5 package has the correct version and depends on all libraries. Your rejections are based on a wrong assumption https://build.opensuse.org/request/show/966082 https://build.opensuse.org/request/show/966084 The only disadvantage is that it also installs the command line tools. I could only see that as a valid reason for rejection in the vtk specifel, because you could want to keep a shlib package pure shlibs. https://build.opensuse.org/request/show/966086 On the other hand a more complex expression to get the correct soversion would be possible, but I am sure you won't like that either. $ rpm -E 'Requires: %(rpm -q --requires hdf5 | grep 'libhdf5-[0-9]*')' Requires: libhdf5-103 = 1.10.8
On the other hand, HDFGroup has adjusted their versioning policy and relaxed the check: https://github.com/HDFGroup/hdf5/pull/1494/files
I.e. we can now (hopefully) rely on the soversion, which should be bumped when major/minor changes, but can be kept when only the release changes.
This is not in Factory, yet. The proposed workaround works, and has worked for years. We can and should use it until https://bugzilla.opensuse.org/show_bug.cgi?id=1196014 is ready or an update for the 1.10 release is available. -- You are receiving this mail because: You are on the CC list for the bug.