Bug 125049
| Summary: | misleading usage message: "Please specify either -l, -u, --nox, or package names" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Tom Jones <t.jones> |
| Component: | up2date | Assignee: | Bryan Kearney <bkearney> |
| Status: | CLOSED ERRATA | QA Contact: | Beth Nackashi <bnackash> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHBA-2006-0465 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-07-20 15:13:37 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 179651, 181405 | ||
Blocking rhnupr4u4 and rhnupr3u8 to track the progress of the release Moving bugs to the CanFix List I changed this message to: "Please specify either -l, -u, --register, --configure, or package names as command line arguments." These are the basic operations you can do with up2date. Re-aligning to correct bug trackers Verified on i386, ia64, x86_64, s390, s390x, and ppc using the latest up2date and rhnlib. Packages tested: up2date-4.4.69-8 rhnlib-1.8.7-1 --installall needs to be added to the list of command line options. It no longer requires the --channel argument. --installall=<channel label> now listed as a possible options. The crux of the matter was that certain combinations of --channel & --installall could end up w/ up2date thinking "there are no package names to install", and merrily continuing on its way. At some point, logic would say: Do I have any package names to install? The answer would be no. Then it would ask: Are any other minimum-needed options present? The answer would be no. So it would bork. So, 2 things: 1) messaging changed 2) if you hand installall a channel label that is non-existant or excluded via --channel options, an error message will show 3) if the specified channel label has no packages, an error message will show 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 the 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-2006-0465.html |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8 Description of problem: The usage message given by up2date can be misleading. For example, typing "up2date --nox --download", you will be told "Please specify either -l, -u, --nox, or package names as command line arguments." But one of those was specified as an argument, so the message needs to be rewritten so as to not be misleading. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.up2date --nox --download 2.read first couple of lines of usage message Actual Results: Output included: "Please specify either -l, -u, --nox, or package names as command line arguments." Expected Results: Not sure what the exact logic is for up2date's arguments, but I imagine a message like "either -l, -u or package names must be specified when using the --nox option" is more correct. Additional info: