Bug 1568 - Upgrading from Mandriva 2010.x using mgaonline does not work
Summary: Upgrading from Mandriva 2010.x using mgaonline does not work
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-06-03 23:30 CEST by Derek Jennings
Modified: 2012-01-18 08:21 CET (History)
6 users (show)

See Also:
Source RPM: mgaonline-2.77.29-1mga
CVE:
Status comment:


Attachments

Description Derek Jennings 2011-06-03 23:30:51 CEST
Description of problem:
The spec file of mgaonline patches mirrors.pm to find the Mageia mirror list, but it does not look in the correct directory


Version-Release number of selected component (if applicable):
mgaonline-2.77.29-1mga

How reproducible:
Every time. Tested on two installations and on a virgin install of 2010.2 in a Virtual Box


Steps to Reproduce:
1. In a computer running Mandriva 2010.x install mgaonline-2.77.29-1mga, log out and log back in again to ensure mgaapplet is running.
2. Observe the Mandriva mirror list remains in place and there is no invitation to upgrade to Mageia
3. From the console the command urpmi.addmedia --distrib --mirrorlist fails with the message it cannot find the mirror list.
4. If the application mgaapplet-upgrade-helper is run in a terminal it can be seen that it is trying to get the mirror list from http://mirrors.mageia.org/api/mageia.2010.2.i586 instead of http://mirrors.mageia.org/api/mageia.1.i586

Looking at the spec file the problem is on line 91

89   %post
90   grep -q pi.mandriva.com/mirror  /usr/lib/perl5/vendor_perl/5.*/urpm/mirrors.pm && \
91    perl -pi -i.bak -e '$_ = "\t\"http://mirrors.mageia.org/api/mageia.\$product_version.\$arch.list\"\n" if m!https://api.mandriva.com/mirrors/!' \
92    /usr/lib/perl5/vendor_perl/5.*/urpm/mirrors.pm || :
93   %{update_desktop_database}
94   %{update_mime_database}

The variable $product_version will be the Mandriva product version 2010.1 or 2010.2 As a result mirrors.pm will look in the wrong directory for the Mageia mirror list. A simple workaround would be to make symlinks on the mageia mirror so for example 
http://mirrors.mageia.org/api/mageia.2010.2.i586 points to http://mirrors.mageia.org/api/mageia.1.i586

There is a second problem with mgaaonline. The default setting is to not check for distribution upgrades so the user has to run mgaapplet-config to enable the check.
Comment 1 Ahmad Samir 2011-06-03 23:34:57 CEST
You're right, the /migrate/ page and the release notes are both wrong.
Comment 2 Thomas Backlund 2011-06-03 23:46:01 CEST
(In reply to comment #0)
> Description of problem:
> The spec file of mgaonline patches mirrors.pm to find the Mageia mirror list,
> but it does not look in the correct directory
> 
> 
> Version-Release number of selected component (if applicable):
> mgaonline-2.77.29-1mga
> 
> How reproducible:
> Every time. Tested on two installations and on a virgin install of 2010.2 in a
> Virtual Box
> 
> 
> Steps to Reproduce:
> 1. In a computer running Mandriva 2010.x install mgaonline-2.77.29-1mga, log
> out and log back in again to ensure mgaapplet is running.
> 2. Observe the Mandriva mirror list remains in place and there is no invitation
> to upgrade to Mageia
> 3. From the console the command urpmi.addmedia --distrib --mirrorlist fails
> with the message it cannot find the mirror list.

This is known not to work (for now).


> 4. If the application mgaapplet-upgrade-helper is run in a terminal it can be
> seen that it is trying to get the mirror list from
> http://mirrors.mageia.org/api/mageia.2010.2.i586 instead of
> http://mirrors.mageia.org/api/mageia.1.i586
> 

You are not supposed to run it manually.

if it gets called by mgaapplet it will get it correctly


> There is a second problem with mgaaonline. The default setting is to not check
> for distribution upgrades so the user has to run mgaapplet-config to enable the
> check.

Are you sure? it worked automatically during qa tests...

CC: (none) => tmb

Comment 3 James Kerr 2011-06-04 01:30:29 CEST
I've just tested in a virgin net-install of mdv 2010.1/2

Installed mgaonline
Logged out/in
5 minutes later the pop-up appeared inviting me to upgrade to Mageia 1
Clicked through the dialogues
It downloaded the hdlists - I saw core and tainted mentioned, and so I knew it was using a Mageia mirror
It then started downloading mga packages

I didn't let it proceed any further
Comment 4 Derek Jennings 2011-06-04 12:24:33 CEST
I tried it again and you are correct Jim. When I was doing it yesterday there were outstanding mandriva updates in which case the pop up window only offers to apply the mandriva updates. There is no pop up offering the upgrade, but right clicking on the applet does show an upgrade is available. If I click on that the upgrade proceeds.

So the only real problem is with the documentation on the web site which does not mention the need to log out and in again, and does not suggest right clicking on the icon if no pop up has appeared after 5 minutes.

As for upgrading through the command line. As Thomas mentions the command
urpmi.addmedia --distrib --mirrorlist  fails.
I found that if I hard coded mirrors.pm to set $product_name=1 then the command works. Applying symlinks to the mirror server to permit product names of 2010.1 and 2010.2 would do the same thing. Wouldn't that be a simple work around?
The alternative is to modify the web instructions to tell users to always use a named mirror.
Comment 5 Vincent R 2011-06-05 12:42:15 CEST
Hello

i'm running a 2010.2 x64 + PLF install ( upgraded from a fresh 2010.1 )

1- I only found the logout + login part here, this need to be put on the upgrades notes

2- While logged in, updating of my mandriva happened, but then nothing
I tried in a terminal and got the same problem of failed mirror as above.

[vincent@localhost ~]$ mgaapplet-upgrade-helper
getting exclusive lock on urpmi
unlocking urpmi database
suppression du média « Main »
suppression du média « Main Updates »
suppression du média « Main32 »
suppression du média « Main32 Updates »
suppression du média « Main Testing »
suppression du média « Main Backports »
suppression du média « Main debug »
suppression du média « Main Updates debug »
suppression du média « Main Testing debug »
suppression du média « Main Backports debug »
suppression du média « Contrib »
suppression du média « Contrib Updates »
suppression du média « Contrib Testing »
suppression du média « Contrib Backports »
suppression du média « Contrib debug »
suppression du média « Contrib Updates debug »
suppression du média « Contrib Testing debug »
suppression du média « Contrib Backports debug »
suppression du média « Non-free »
suppression du média « Non-free Updates »
suppression du média « Non-free Testing »
suppression du média « Non-free Backports »
suppression du média « debug_non-free_release »
suppression du média « debug_non-free_updates »
suppression du média « debug_non-free_testing »
suppression du média « debug_non-free_backports »
suppression du média « Restricted »
suppression du média « Restricted Updates »
suppression du média « PLF Free »
suppression du média « PLF Free debug »
suppression du média « PLF Free backports »
suppression du média « PLF Free backports debug »
suppression du média « PLF Non-free »
suppression du média « PLF Non-free debug »
suppression du média « PLF Non-free backports »
suppression du média « PLF Non-free backports debug »
not using outdated cached mirror list $MIRRORLIST
URPMI_ADDMEDIA_REASON reason=update
récupération de la liste des miroirs depuis http://mirrors.mageia.org/api/mageia.2010.2.x86_64.list?reason=update
  mageia.2010.2.x86_64.list?reason=update récupéré
géolocalisation trouvée FR 48.87 2.33 du fuseau horaire Europe/Paris
Fatal: Impossible de trouver un miroir dans la liste $MIRRORLIST
Unknown option: nocheck
    ftp://ftp.free.fr/mirrors/ftp.mandriva.com/MandrivaLinux/official/2010.1/x86_64/media/main/release/media_info/20101215-022731-synthesis.hdlist.cz
... échec de la récupération : curl: (28) FTP response timeout                                                   
... échec de la récupération : curl a échoué : sortie avec 28
problème de lecture du fichier de synthèse du média « Main »
... échec de la récupération : curl a échoué : sortie avec 28

CC: (none) => vortex_fr

Manuel Hiebel 2011-06-07 12:37:33 CEST

CC: (none) => mageia-webteam

Comment 6 Derek Jennings 2011-06-07 17:40:05 CEST
I notice the instructions on the website have been adjusted. It now lists the command to get the media sources as
"urpmi.addmedia --distrib http://mirrors.mageia.org/api/mageia.1.$ARCH.list"

That is not quite correct. It should be
"urpmi.addmedia --distrib --mirrorlist http://mirrors.mageia.org/api/mageia.1.$ARCH.list"
Comment 7 Romain d'Alverny 2011-06-07 18:11:43 CEST
(In reply to comment #6)
> That is not quite correct. It should be
> "urpmi.addmedia --distrib --mirrorlist
> http://mirrors.mageia.org/api/mageia.1.$ARCH.list"

Ah right, sorry for the typo, fixed; thanks!

CC: (none) => rdalverny

AL13N 2011-06-07 19:45:27 CEST

CC: (none) => maarten.vanraes

Comment 8 AL13N 2011-09-05 08:43:19 CEST
can the applet not working well be a result of bug 2317?
Comment 9 Manuel Hiebel 2011-10-16 00:47:46 CEST
hello, what is the status of this bug ?
Comment 10 Marja Van Waes 2011-12-11 15:41:27 CET
(In reply to comment #9)
> hello, what is the status of this bug ?

Is this bug still valid?

Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD. Thank you.

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 11 AL13N 2011-12-11 16:42:16 CET
actually, since this is a mdv upgrade issue, i assume mdv upgrades aren't supported in 2 or cauldron, only 1, so either we fix this for 1 or we close as OLD?
Comment 12 Marja Van Waes 2012-01-18 08:21:06 CET
(In reply to comment #11)
> actually, since this is a mdv upgrade issue, i assume mdv upgrades aren't
> supported in 2 or cauldron, only 1, so either we fix this for 1 or we close as
> OLD?

And the past months no one confirmed it still exists, so either no one chooses this way to upgrade anymore, or it got fixed :)

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


Note You need to log in before you can comment on or make changes to this bug.