Description of problem: Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1.run up2date 2. 3. Actual results: Error window during up2date checkin when trying to update several packages. Some update fine. Others look for files that aren't there. Up2date aborts when it encounters this situation. Expected results: clean system update Additional info: This is the error as it pertains to krb5 update from 1.2.7-10 to 1.2. 7-14: Error window during up2date checkin: There was a fatal error communicating with the server. The message was: File Not Found: r-e-d.a
Error window during up2date checkin: There was a fatal error communicating with the server. The message was: File Not Found: r-e-d.a Error Message: Invalid RPM package krb5-1.2.7-14.src.rpm requested Error Class Code: 17 Error Class Info: File not found. Explanation: An error has occurred while processing your request. If this problem persists please enter a bug report at bugzilla.redhat.com. If you choose to submit the bug report, please be sure to include details of what you were trying to do when this error occurred and details on how to reproduce this problem. From Command-line up2date -u Fetching package list for channel: redhat-linux-i386-9... ######################################## Fetching Obsoletes list for channel: redhat-linux-i386-9... ######################################## Fetching rpm headers... ######################################## Testing package set / solving RPM inter-dependencies... ######################################## krb5-devel-1.2.7-14.i386.rp ########################## Done. File Not Found: r-e-d.a Error Message: Invalid RPM package krb5-1.2.7-14.src.rpm requested Error Class Code: 17 Error Class Info: File not found. Explanation: An error has occurred while processing your request. If this problem persists please enter a bug report at bugzilla.redhat.com. If you choose to submit the bug report, please be sure to include details of what you were trying to do when this error occurred and details on how to reproduce this problem.
*** This bug has been marked as a duplicate of 115693 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.