A non-zero exit code is returned for a missing package when --skip-broken used. The available package is not installed. Reproducible: Always Steps to Reproduce: dnf install -y --skip-broken tree forest echo $? Actual Results: Failed to resolve the transaction: No match for argument: forest # echo $? 1 Expected Results: tree package installed, missing forest ignored and 0 returned dnf5-5.0.14-1.fc39.x86_64
The --skip-broken is in DNF5 split between --skip-broken (to skip packages uninstallable due to depsolv problems) and --skip-unavailable (to skip packages unavailable in repositories). The change is documented here: https://github.com/rpm-software-management/dnf5/blob/main/doc/changes.rst#strict-configuration-option-deprecation (this describes the "strict" configuration option, but --skip-broken was an alias for it).
So in your case try `dnf5 install -y --skip-unavailable tree forest`. I discovered a gap in the dnf5 install command man pages - these options are not documented - upstream issue https://github.com/rpm-software-management/dnf5/issues/644.
Thanks for the info. Just wonder, doesn't the "old" --skip-broken behaviour cover quite a frequent use case? This seems like a backward-incompatible change which will affect many users, I'd say.
Why dnf is changing behavior of --skip-broken, rather then preserving it? This change broke our test infrastructure on many place and we see huge risks it will affect Fedora/CentOS Stream/RHEL users and customers. changes.rst mention that strict config option was a problem that it did two things - but we see it as benefit do these together. Is there any issue introducing --skip-uninstallable and --skip-unavailable while keeping --skip-broken ?
Also with introducing this incompatilibity, customers which have mutiple versions of RHEL would need to start maintaining RHEL release specific scripts/config
# dnf5 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments. # rpm -qa | grep dnf5 libdnf5-5.0.15-2.fc39.x86_64 libdnf5-cli-5.0.15-2.fc39.x86_64 dnf5-5.0.15-2.fc39.x86_64 dnf5-plugins-5.0.15-2.fc39.x86_64
The issue with the position of the argument is being discussed in related bugzilla there: https://bugzilla.redhat.com/show_bug.cgi?id=2216055.
Can you please provide ETA for resolution of this regression? It causes stability issues in our CI/Testing pipelines.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.