-
I hope this is the right tracker to post this. I'm building a package that has a hard requirement on a specific package, but when installing the RPM, it doesn't get updated. SPEC snippet:
When I check the RPM requirements, I can see the correct version:
Then I instal the package with dnf install , but it will only install
The required version is available in the repos:
According to http://ftp.rpm.org/api/4.4.2.2/dependencies.html and http://ftp.rpm.org/max-rpm/s1-rpm-depend-manual-dependencies.html, configuration is correct. I also looked at some SRPMS from distro and the configuration is the same. What am I doing wrong? I can't see the issue, thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Impossible to say for sure without full dependency details of the package set in question. Requires is just one side of the equation, provides are just as important. One possibility is that you have an unversioned provide of datacenter-gpu-manager somewhere, that would satisfy all possible version requirements. Or an accidental versioned datacenter-gpu-manager provide somewhere that is satisfied. Running the upgrade with 'rpm -Uvv' will spit out a log of debug information, among which should be the answer (or at least clue) to your question. |
Beta Was this translation helpful? Give feedback.
Yes, like I said an unversioned provides will match any version at all, and there's nothing the requiring side can do about it.
The only way around that is to require something else that only the newer package provides.