Unacceptable up2date functionality

[Douglas Stewart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Due to Rawhide's absence since yesterday, I've noticed that up2date is
COMPLETELY user-unfriendly when it can't reach a yum repo.  Instead of
printing any error messages to the tune of "I can't reach that repo.
Sorry!", it simply spits cryptic Python errors to the terminal window
and hangs the progress window, while moving the main window to "Packages
to be skipped".

I would suggest that, in such cases, up2date offer up something akin to
the dialog the user encounters when no updates are needed (i.e., " Can't
reach any of the listed repositories.  Please check your network
settings and try again later".)
- --
- ----------
Doug Stewart
Systems Administrator/Web Applications Developer
Lockheed Martin Advanced Technology Labs

Quidquid latine dictum sit, altum viditur
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/lth4N50Q8DVvcvkRAiJPAJ4h6SD2aR/EtYzlGwBP3YHTjT5tiwCfTzlC
mU/e1KSsx7ti27hwp89cDhk=
=N0Bk
-----END PGP SIGNATURE-----