Bug 773512 - yum --enablerepo downloads metadata too early
Summary: yum --enablerepo downloads metadata too early
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 796757 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-12 05:28 UTC by Joachim Backes
Modified: 2015-06-20 07:22 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-19 19:38:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Joachim Backes 2012-01-12 05:28:16 UTC
Description of problem:

I made a yum call with a typo:

yum upodate kernel --enablerepo=updates-testing (I meant ... update ...)

It seems yum does a lot of not useful things before it sees the syntax error:

yum upodate kernel --enablerepo=updates-testing
Loaded plugins: langpacks, presto, refresh-packagekit
------ begin of my comment: this part not needed!!!!!!!!!!!!!!!!!!!!!-----------
updates-testing/metalink                                 |  18 kB     00:00     
updates-testing                                          | 4.7 kB     00:00     
updates-testing/primary_db                               | 1.5 MB     00:01     
updates-testing/group_gz                                 | 431 kB     00:00
------ end of my comment: this part not needed!!!!!!!!!!!!!!!!!!!!!-------     
No such command: upodate. Please use /usr/bin/yum --help


Version-Release number of selected component (if applicable):
------ my comment: not needed!!!!!!!!!!!!!!!!!!!!!-----------

How reproducible:
always

Steps to Reproduce:
1.enter a yum cmd with a syntactically wrong subcommand
2.
3.
  
Actual results:
No immediate syntax check

Expected results:
immediate syntax check

Additional info:

Comment 1 Zdeněk Pavlas 2012-02-24 07:17:37 UTC
*** Bug 796757 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.