Bug 1174612
| Summary: | RFE: backport --assumeno option to yum | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Paul Wayper <pwayper> |
| Component: | yum | Assignee: | Valentina Mukhamedzhanova <vmukhame> |
| Status: | CLOSED ERRATA | QA Contact: | Karel Srot <ksrot> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.6 | CC: | byount, james.antill, ksrot, pwayper, salmy, vmukhame |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | yum-3.2.29-65.el6 | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-22 07:21:43 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: | |||
Since yum already supplies this information in human-readable format and the output can be grepped, I believe if we backport --asumeno that would be sufficient for this request? --assumeno Assume no; assume that the answer to any question which would be asked is no. This option overrides assumeyes, but is still subject to alwaysprompt. Configuration Option: assumeno Hi Valentina, How much detail does yum actually get? Can it give an output per mount point? For the customer that originally raised this issue, this would be more useful - but the aggregate download and installed space requirements would be acceptable. The main thought of having a separate output is just to save using grep and/or having it mis-trigger - e.g. 'yum install perl-Image-Size | grep -i size' is going to get confused with false positive lines. It also saves a bunch of output that isn't necessary for the final result. Backporting --assumeno plus writing a KCS article to detail how to use this option plus grep to get size calculations would be a reasonable compromise. Thanks, Paul Hi Paul, No, it doesn't have a per mount point information, it only has size for each package. Thank you for the details, I'll look into backporting --assumeno. I accept that back-porting the --assumeno flag is the best practical solution. Thanks, Paul 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://rhn.redhat.com/errata/RHBA-2015-1384.html |
Description of problem: Yum has the ability to determine the download size and the installed size of an install, upgrade or remove operation. However, this is only made available in the information provided at the interactive prompt. For automated upgrades, it would be useful to supply this information either in human-readable format or in some kind of machine-readable format (e.g. JSON or YAML). This can then be read into standard configuration management utilities - e.g. Puppet - to make sure that an update only occurs when it is has enough space. It would also be useful to break this down into space required per file system. Version-Release number of selected component (if applicable): yum-3.2.29-43.el6_5.noarch How reproducible: Always Steps to Reproduce: 1. Find a package you don't have installed on your system. 2. yum install ${missing_package} | grep size Actual results: Total download size: 9.8 M Installed size: 42 M Expected results: download_size=9812345 installed_size=42123456 Additional info: