Bug 1717429
Summary: | dnf install errors out when a non-existent package is provided together with existing ones | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Daniel Mach <dmach> |
Component: | dnf | Assignee: | Daniel Mach <dmach> |
Status: | CLOSED ERRATA | QA Contact: | Eva Mrakova <emrakova> |
Severity: | unspecified | Docs Contact: | Marie Hornickova <mdolezel> |
Priority: | medium | ||
Version: | 8.1 | CC: | james.antill, kwalker, lmanasko, mdomonko |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
.*YUM v4* requires all packages specified with `yum install` to be available
*YUM v4* validates all arguments of the `yum install` command. Consequently, if any argument does not match an existing package, *YUM v4* exits and does not install packages that match.
This behavior differs from *YUM v3* on RHEL 7 where the matching packages were installed in such situation. To work around the problem and make the matching packages installed, use the `--skip-broken` argument together with `yum install`.
For more information, see link:https://access.redhat.com/solutions/4222871[Why does "yum install <package1> <package2>", where the "<package2>" identifier doesn't exist, cause the transaction to fail in Red Hat Enterprise Linux 8?] Knowledgebase article.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-05 22:22:10 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1681084 | ||
Bug Blocks: |
Description
Daniel Mach
2019-06-05 13:12:03 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3583 |