Bug 10047

to check for mga3>4

CC: (none) => manuel.mageia
Assignee: bugsquad => thierry.vignaud

seems this test http://svnweb.mageia.org/soft/drakx/trunk/perl-install/install/steps_interactive.pm?&view=markup#l135

@l = grep { $_->{arch} eq $arch && $_->{version} !~ /201[1-9]/ } @l;
if (@l) {
_try_to_upgrade($o, @l);
}

and for the other comment is in the same part too

Keywords: (none) => Junior_job
Version: 2 => Cauldron

(In reply to Lewis Smith from comment #0)
> Description of problem:
> 
> On a system with existing Mageia(s), the Installer offers to UPGRADE the
> other(s) or Install from scratch. Even if the other systems are more
> recent...
> 1) Most serious, the Mag2 Installer offers to update another Mag3!
> 2) But the Mag3 Installer also offers to Upgrade an existing Mag3 - which is
> unlikely to be meaningful.
> I was using both Mag2 & Mag3 full 32-bit Install DVDs.
> 


Upgrading borked systems with the same version is something I've done several times. IIRC, it always fixed the problems :-)

I'd appreciate it that remains possible

CC: (none) => marja11

Can this be closed - invalid?

(In reply to Lewis Smith from comment #4)
> Can this be closed - invalid?

Well, the other part, it offering to upgrade a newer version, would be OK to have fixed, if it hasn't already.

Maybe you can change an existing Mageia on your HD into a fake Mageia 6 install to see whether it still happens with 5beta3. I assume (but did not check!) installer reads /etc/mageia-release to determine the version.

Testing with the MGA5 Classical installer in all archs (i586 & x64) and faking MGA6

CC: (none) => neoser10

Would it be a good idea to add an extra install option; Repair Existing?

This could appear when a 'same version' is detected, and perhaps run a reinstall of installed packages.

CC: (none) => luke.nukem.jones

Have just followed Marja's note from Comment 3:
> Upgrading borked systems with the same version is something I've done several
> times. IIRC, it always fixed the problems :-)
> I'd appreciate it that remains possible
Using the Mageia 5 Classic Installer to update my more up-to-date but *broken* Mageia 5 (EFI unbootable) did indeed bring it back to life - but not without some head-scratching & misbehaviour. Big thanks for that tip.

So this *is* an important ability: Comment 7 is just:
> Would it be a good idea to add an extra install option; Repair Existing?
> This could appear when a 'same version' is detected
And needs to be both documented, & noted in the Installer itself when it recognises such a situation.
I have always complained that this 'update' facility:
- previous version, to upgrade it
- same version to revive it
should be on the boot menu rather than something you discover by chance along the way.

OTOH If by ill chance the Installer finds a *more recent* Mageia version, it certainly should *not* offer to update it. I imagine that would be disastrous. I was wanting to close this bug, but this last point does need to be fixed if still extant. Comment 5 supports this view:
> Well, the other part, it offering to upgrade a newer version, would be OK
> to have fixed, if it hasn't already.

Once pre-release Mageia 6 becomes installable, I will try the M5 Classic Installer to see whether it offers to update M6.

Although logically this bug is legitimate - it makes little sense to offer to upgrade a Mageia installation more recent than the installer - this behaviour *does* have a useful spin-off in being able to revive an existing unbootable Mageia installation. Essentially, the whole 'update' process is skipped because there is nothing to do, BUT the bootloader is re-installed. A lifesaver if the result then re-boots successfully.
Closing this WONTFIX on Marja's recommendation; with which I agree.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX