/u/aiwendilh said this
http://rpm.org/api/4.4.2.2/dependencies.html RPM has a "conflict" dependency relationship...that does pretty much what you say. If A conflicts B then A can't be installed together with B. I think pretty much every package manager has conflicting dependencies. debs have "conflicts" too and ebuilds have blockers (basically boolean operations for dependencies so ! means blocked by that dependency) Edit: Pacman part was wrong..it offers conflicts as well.
The basic docs are here:
https://rpm.org/user_doc/more_dependencies.html#automatic-dependencies
http://rpm.org/user_doc/dependency_generators.html
My guess is your package probably contains an executable file with a shebang line (#!/usr/bin/python
). A few suggested fixes are here:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_shebang_lines
>They are dependencies one way and supplements the other :D Whether you choose to install yast-theme-oxygen itself or oxygen5-icons and yast-theme, you will end up with yast-theme-oxygen.
Right. I think that makes sense. So essentially what you are saying that supplementary is a type of dependency. Re-reading the section on dependencies at http://rpm.org/user_doc/dependencies.html and the description lends to clarifying the definition.
Weak: By default the dependency solver shall attempt to process the dependency as though it were strong. If this is results in an error then they should be ignored and not trigger an error or warning.
Since supplements is a weak dependency it'll continue to install package in the event of failure. I imagine that the program/application may not function as intended.
I'll have to keep reading it again multiple times. It's unfortunate that no real-world examples are provided.
Yeah, I take it this was from the rpm website? Unfortunately I had tried this in the past. I'm not even sure why it's not working, I ran;
rm -rf /var/lib/rpm/__db* /var/lib/rpmrebuilddb* /usr/lib/rpm/rpmdb_verify /var/lib/rpm/Packages
Good, up to this point, no errors and the Packages file is successfully verified!
rpm -v --rebuilddb
No output, but upon doing;
rpm -qa
Still nothing returns. RPM database empty, yum updates still fail. Wish I knew where to look for a log or something on why this wasn't successful (or at least why I'm not getting the results I want.)
I appreciate your help though!
I don't think its very beginner friendly but I fell back a lot on the official RPM manual