I think the text of the dialog windows are not clear enough to warn that this process, if not done correctly, can make your system inaccessible, requiring a reinstall.
And I think that it is not clear how to choose the option: do not update the version. Select the option to cancel is enough? It seems that no.
Select "do not ask me next time" and after "cancel" or after "next" or close the window?
I refer mainly to this dialog:
I mention this subject in the Forum Mageia (en), on the topic:
Distribution Upgrade Mageia 1 to Mageia 2
Maybe we could add the checkbox equivalent to --auto, no?
I agree, it needs some improvement, i was nt sure if i had to click on a checkbox before click on next or not.
The texts of the dialog windows of Mageia Upgrade are not clear enough =>
upgrade dialog are not clear enough
Assigning this enhancement request to the Mageia Tools maintainer group. I must confess I haven't checked if the dialog has been improved since the bug was reported.
upgrade dialog are not clear enough =>
mgaonline upgrade dialog could be made more obviousPriority:
15637, 8016 =>
Mageia 3 =>
Upgrade dialog should be improved.
But, User should remember that when there is a N+1 release, the N release will be EOL 3 months after N+1 release date. So, the mgaapplet warning about new version available should not have a "don't ask again" box. Moreover, there is already a switch in MCC => Software => Configure updates frequency to prevent displaying new distribution version.
According to the original bug report, the enhancement request is about to add a "download-all" switch before playing RPM transaction, in order to minimize the Network going offline issue on poor connection.
Should also prevent upgrading when some 32 bits devel RPM are installed on the migrating candidate system: this is a know bug that i586 devel RPM will conflict with x86_64 ones.
(In reply to Aurelien Oudelet from comment #4)
> According to the original bug report, the enhancement request is about to
> add a "download-all" switch before playing RPM transaction, in order to
> minimize the Network going offline issue on poor connection.
Part of the problem is that the upgraded version of rpm/urpmi may resolve
dependencies differently than the current version, so currently, even if
download all is selected, it's broken into two parts. Priority updates
which includes things like glibc, perl, rpm and urpmi, and anything else needed
to get the new version of gurpmi to work, after which it restarts gurpmi and
then selects/downloads the rest of the packages.
I don't think this can be avoided, but the gui should explain this so the
user doesn't think it aborted and restarted from scratch.
> Should also prevent upgrading when some 32 bits devel RPM are installed on
> the migrating candidate system: this is a know bug that i586 devel RPM will
> conflict with x86_64 ones.
It shouldn't prevent it. On a x86_64 install, just display a very strong
warning requiring confirmation with, three options selectable:
- remove all i586 devel packages
- continue at own risk
with remove being the default.
The same should likely be done for all debug packages on both i586 and x86_64
The system may have third party i586 devel and/or debug packages installed that
will not interfere with the upgrade, but that's up to the admin to determine,
hence the option to continue at own risk.