Bug 1497351
Summary: | [RFE] yum versionlock should give a note, if packages are blocked by update | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Steffen Froemer <sfroemer> |
Component: | yum-utils | Assignee: | Michal Domonkos <mdomonko> |
Status: | CLOSED ERRATA | QA Contact: | Eva Mrakova <emrakova> |
Severity: | low | Docs Contact: | Marie Hornickova <mdolezel> |
Priority: | low | ||
Version: | 7.4 | CC: | emrakova, james.antill, mdomonko, packaging-team-maint, tbowling, vmukhame |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | yum-utils-1.1.31-50.el7 | Doc Type: | Release Note |
Doc Text: |
The "yum versionlock" plug-in now displays which packages are blocked when running the "yum update" command
Previously, the "yum versionlock" plug-in, which is used to lock RPM packages, did not display any information about packages excluded from the update. Consequently, users were not warned that such packages will not be updated when running the "yum update" command. With this update, "yum versionlock" has been changed. The plug-in now prints a message about how many package updates are being excluded. In addition, the new "status" subcommand has been added to the plug-in. The "yum versionlock status" command prints the list of available package updates blocked by the plug-in.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 11:40:47 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: | |||
Bug Blocks: | 1549618 |
Description
Steffen Froemer
2017-09-29 21:15:51 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/RHBA-2018:3280 |