Description of problem: New packages that are supplements of another (already installed) package are pulled only when the original package is being upgraded or reinstalled. This is a problem in some cases, for example if a newly added repository has AppStream metadata packages (to enable users to install packages using GNOME Software/KDE Discover) that are supplements of the original Fedora appstream-data package. Please, consider fixing this. Additional info: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/YJFNPX2LA3DQPLOR55EIVYH4TNUTIIIS/
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
Any news?
I expect this is the case in all Fedoras. Bumping to rawhide.
So here is nothing to do from libsolv side, it doesn't know if the package was excluded/broken or it just appeared in the repo, so it doesn't take any action. DNF should implement install-new-recommends command.
How about install-new-weak-deps? It can be be also Supplements, correct?
(In reply to Daniel Mach from comment #5) > How about install-new-weak-deps? Please make it same as in other package managers -- install-new-recommends. > It can be be also Supplements, correct? Yes. You need to set solverflags to "addalreadyrecommended" and do empty transaction.
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle. Changing version to '30.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
Still the same problem.
(Can be reproduced by adding RPM Fusion.)
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.