Red Hat Bugzilla – Bug 818280
'yum localupdate' in RHEL6 requires full path
Last modified: 2014-01-21 01:25:04 EST
Description of problem:
'yum localupdate' in RHEL6 requires full path. However, in RHEL5, 'yum localupdate' did not require the full path. Could the behaviour be changed in RHEL6 to the way it is in RHEL5?
Version-Release number of selected component (if applicable):
Download updates to a folder in RHEL6. Attempt to yum update from the folder using 'yum localupdate *.rpm'.
Steps to Reproduce:
1. Download updates to a folder.
2. Navigate to that folder.
3. Run this command 'yum localupdate *.rpm'
System does not get updated and the following error occurs:
TypeError: an integer is required
error: python callback <bound method RPMTransaction.callback of <yum.rpmtrans.RPMTransaction instance at 0x3e8f290>> failed, aborting!
Packages should get updated to the versions that are in the folder.
1. Proposed title of this feature request
Change behaviour of 'yum localupdate' to not require the full path.
2. Who is the customer behind the request?
Account name: Momentum
TAM/SRM customer: no
Strategic Customer yes/no: no
3. What is the nature and description of the request?
When using 'yum localupdate' to update in RHEL6, you are required to use the full path. In RHEL5, 'yum localupdate' does not require the full path. Customer would like for the behaviour in RHEL6 to be the same as RHEL5.
4. Why does the customer need this? (List the business requirements here)
Customer's servers are behind firewall which limit our access to RedHat Network and we are required to download update first and then do local update at a later time.
5. How would the customer like to achieve this? (List the functional
'yum localupdate' with a relative path should work as before in RHEL 5.
6. For each functional requirement listed in question 5, specify how Red Hat
and the customer can test to confirm the requirement is successfully
Be able to update the system, using 'yum localupdate' and relative path.
7. Is there already an existing RFE upstream or in Red Hat bugzilla?
8. Does the customer have any specific timeline dependencies?
Within one month will be better.
9. Is the sales team involved in this request and do they have any additional input?
10. List any affected packages or components.
11. Would the customer be able to assist in testing this functionality if
Will be able to assist in testing.
*** Bug 810117 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 746190 ***