Bug 6068

Summary:	mgaonline upgrade dialog could be made more obvious
Product:	Mageia	Reporter:	macxi <terraagua>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	davidwhodgins, dglent, marcello.anni, ouaurelien, pmdenielou, stormi-mageia, thierry.vignaud
Version:	Cauldron	Keywords:	Junior_job, Triaged
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	https://forums.mageia.org/en/viewtopic.php?f=29&t=2506
Whiteboard:
Source RPM:	mgaonline	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	28736

Description macxi 2012-05-24 15:47:32 CEST

Hi, 
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:
http://dl.dropbox.com/u/1220932/mg/mga-2/upgrade-mga1-to-mga2/configure-updates-frequency-004.jpg

I mention this subject in the Forum Mageia (en), on the topic:
Distribution Upgrade Mageia 1 to Mageia 2
https://forums.mageia.org/en/viewtopic.php?f=29&t=2506

macxi 2012-05-24 15:59:15 CEST

Priority: Normal => Low

Comment 1 Malo Deniélou 2012-05-24 16:01:56 CEST

Maybe we could add the checkbox equivalent to --auto, no?

CC: (none) => malo

macxi 2012-05-24 16:07:12 CEST

Target Milestone: --- => Mageia 3

Comment 2 Dimitrios Glentadakis 2012-05-24 16:16:39 CEST

I agree, it needs some improvement, i was nt sure if i had to click on a checkbox before click on next or not.

CC: (none) => dglent

Manuel Hiebel 2012-05-25 10:58:53 CEST

CC: (none) => thierry.vignaud
Source RPM: (none) => mgaonline
Keywords: (none) => Junior_job
Component: Installer => RPM Packages

Marcello Anni 2012-06-25 17:05:35 CEST

CC: (none) => marcello.anni

Manuel Hiebel 2012-11-08 16:07:06 CET

Blocks: (none) => 8016

macxi 2012-12-18 13:57:17 CET

Summary: The texts of the dialog windows of Mageia Upgrade are not clear enough => upgrade dialog are not clear enough

Samuel Verschelde 2013-08-28 15:01:52 CEST

CC: (none) => stormi
Keywords: (none) => Triaged

Manuel Hiebel 2013-10-11 23:38:36 CEST

Version: 2 => Cauldron

Marja Van Waes 2015-04-06 23:08:41 CEST

Blocks: (none) => 15637

Comment 3 Samuel Verschelde 2016-10-15 16:24:19 CEST

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.

Summary: upgrade dialog are not clear enough => mgaonline upgrade dialog could be made more obvious
Priority: Low => Normal
Blocks: 15637, 8016 => (none)
Assignee: bugsquad => mageiatools
Target Milestone: Mageia 3 => ---

Comment 4 Aurelien Oudelet 2021-05-12 18:12:50 CEST

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.

CC: (none) => ouaurelien
Hardware: i586 => All
Blocks: (none) => 28736

Comment 5 Dave Hodgins 2021-05-12 20:58:04 CEST

(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
 - abort
 - 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
upgrades.

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.

CC: (none) => davidwhodgins