Running preupgrade when the network is down (e.g. before association with wireless) yields the following traceback if run from a terminal: Traceback (most recent call last): File "/usr/share/preupgrade/preupgrade-gtk.py", line 750, in <module> widgets = PreUpgradeGtk() File "/usr/share/preupgrade/preupgrade-gtk.py", line 313, in __init__ self.pu = preupgrade.PreUpgrade() File "/usr/lib/python2.5/site-packages/preupgrade/__init__.py", line 267, in __init__ self.release_map = self.retrieve_release_info(configfile) File "/usr/lib/python2.5/site-packages/preupgrade/__init__.py", line 321, in retrieve_release_info configdata = grabber.urlopen(configfile) File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 890, in urlopen return self._retry(opts, retryfunc, url) File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 851, in _retry r = apply(func, (opts,) + args, {}) File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 889, in retryfunc return URLGrabberFileObject(url, filename=None, opts=opts) File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 1007, in __init__ self._do_open() File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 1086, in _do_open fo, hdr = self._make_request(req, opener) File "/usr/lib/python2.5/site-packages/urlgrabber/grabber.py", line 1215, in _make_request raise URLGrabError(4, _('IOError: %s') % (e, )) urlgrabber.grabber.URLGrabError: [Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')> When run from the GUI, no indication is given that the application even started. Instead, some form of GUI error message should be displayed indicating that the application did in fact actually run, and that an error occurred. preupgrade-1.0.0-1.fc9.noarch
Yup, that's what happens all right. We need to contact the network to be able to see what upgrades are available, so the network is definitely required, but we should handle this a little more cleanly.
preupgrade-1.1.0-0.pre2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/preupgrade-1.1.0-0.pre2.fc10
preupgrade-1.1.0-0.pre2.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update preupgrade'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-4211
preupgrade-1.1.0-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/preupgrade-1.1.0-1.fc9
preupgrade-1.1.0-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/preupgrade-1.1.0-1.fc11
preupgrade-1.1.0-1.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update preupgrade'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-4211
preupgrade-1.1.0-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
preupgrade-1.1.0-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
preupgrade-1.1.0-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.