From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 Description of problem: Rawhide downtime has caused a nasty user-unfriendly condition to crop up in up2date. When a repo can't be reached, a mess of Python errors are spewed to the terminal and up2date-gnome proceeds to "Packages Marked to Skip" dialog, yet the progress dialog just hangs indefinitely. Such a condition should produce a dialog similar to the one that up2date produces when no updates are available. Version-Release number of selected component (if applicable): up2date-4.1.7-1 How reproducible: Always Steps to Reproduce: 1. Run up2date when main yum repo is unavailable 2. Watch for Python errors and lack of dialog 3. Rinse, repeat Actual Results: Nasty Python messages written to terminal, no dialog produced. Expected Results: A dialog informing the user of something to the extent of "I'm sorry. I can't reach that repository" should be printed and no Python errors should go to STDOUT/STDERR. Additional info:
*** This bug has been marked as a duplicate of 107732 ***
available in 4.1.9/10 when rawhide comes back
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.