diff options
| author | Radek Vykydal <rvykydal@redhat.com> | 2009-08-05 16:39:26 +0200 |
|---|---|---|
| committer | Radek Vykydal <rvykydal@redhat.com> | 2009-08-05 16:51:37 +0200 |
| commit | d09f40b03a1da5ab530c4857d9cb21545e155852 (patch) | |
| tree | 09016c0d8a426d5444fbb27025572356843f856e /yuminstall.py | |
| parent | 18d4d9d681fe4edb59c37bb8c65d78f5e1b4b4c7 (diff) | |
| download | anaconda-d09f40b03a1da5ab530c4857d9cb21545e155852.tar.gz anaconda-d09f40b03a1da5ab530c4857d9cb21545e155852.tar.xz anaconda-d09f40b03a1da5ab530c4857d9cb21545e155852.zip | |
Do not offer going back when ugrade root for ks upgrade is not found (#499321)
Going back results in traceback which seems not right. Bug 499321 (preupgrade
backtrace) has lots of tracebacks with various causes of upgrade root not found
- I distincted two groups.: 1) dmraid not detected in f10 (=> installation on
2 disks) while detected in f11 (=> root not found). 2) root considered as
non-upgradable (/etc/redhat-release changed by user). Such a broad bug is
rather difficult to handle. OTOH we wouldn't get the tracebacks so easy if we
just ended with error message (as with the patch).
Diffstat (limited to 'yuminstall.py')
0 files changed, 0 insertions, 0 deletions