Bug 474826
Summary: | yum install prints confusing statements when in quiet mode | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | David Kovalsky <dkovalsk> |
Component: | yum | Assignee: | James Antill <james.antill> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | benl, bperkins, gkhachik, jhutar, rlerch |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, when in quiet mode, yum would not print details of the transaction, only the prompt "Is this ok [y/N]". Under certain circumstances, messages from plugins (such as the RHN plugin) might appear directly above the prompt in quiet mode and make it appear as if the prompt were related to the message from the plugin rather than to the transaction. Yum now always prints details of the transaction -- even in quiet mode -- so that it is always obvious to what the prompt is referring.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-02 07:34:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Kovalsky
2008-12-05 14:56:49 UTC
so, if we add more output when you specify -q then we'll end up causing pain for all the people who use -q to silence yum for cron jobs. In the above scenario, rhn plugin should really be exiting the whole process if the system is not registered. It shouldn't be allowing it all to continue. A failure to reach a repo (including rhn) is a fatal error, imo. Currently a failure to reach an RHN repo is ignored, I'm not sure, but there was some bug to *get* this behaviour, so change could be an regression (maybe these: bug 378911 and bug 435840 could be related). We fixed this by always printing the transaction if assumeyes wasn't on. # VERIFIED The "[y/N]" option now displays in a proper place and not right after the message about "RHN support disabled" text. System continues to search for other repositories even when system is not registered to RHN. - Checked on: RHEL5.4-Client-20090715.0 (x86_64, i386); RHEL5.4-Server-20090715.0 (i386, x86_64, ia64, s390x) - Package(s): yum-3.2.22-20.el5 --- # yum -q install vsftpd This system is not registered with RHN. RHN support will be disabled. ====================================================================================================================================================================== Package Arch Version Repository Size ====================================================================================================================================================================== Installing: vsftpd x86_64 2.0.5-16.el5 rhts-custom3 139 k Transaction Summary ====================================================================================================================================================================== Install 1 Package(s) Update 0 Package(s) Remove 0 Package(s) Is this ok [y/N]: n Exiting on user Command --- Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously, when in quiet mode, yum would not print details of the transaction, only the prompt "Is this ok [y/N]". Under certain circumstances, messages from plugins (such as the RHN plugin) might appear directly above the prompt in quiet mode and make it appear as if the prompt were related to the message from the plugin rather than to the transaction. Yum now always prints details of the transaction -- even in quiet mode -- so that it is always obvious to what the prompt is referring. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1419.html |