From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 Description of problem: There was a fatal error communicating with the server. The message was: File Not Found: r-e-d.a Error Message: Invalid RPM package Canna-3.5b2-70.8.0.1.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. Version-Release number of selected component (if applicable): up2date-3.0.7-1 How reproducible: Always Steps to Reproduce: 1. run up2date Actual Results: There was a fatal error communicating with the server. The message was: File Not Found: r-e-d.a Error Message: Invalid RPM package Canna-3.5b2-70.8.0.1.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. Expected Results: no problems with any other files, should act same here... Additional info:
Getting the same report for evolution 1.0.8-11: in running up2date on version 8.0-i686, got the following message. This has been repeatable over three days. There was a fatal error communicating with the server. The message was: File Not Found: r-e-d.a Error Message: Invalid RPM package evolution-1.0.8-11.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 101250 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.