Running the following as root clears the RPM sources, downloads new ones and displays a Congratulations window saying that the "Upgrade to Mageia release was successfull." (I left in the extra space and spelling error). #mgaapplet-upgrade-helper --new_distribution_version=2 It does not upgrade to Mageia 2 however, nor does it give an error. It sets all of the sources to the Mageia 1 sources. Using the argument "new_distro_version" does work. Thank you, Jeff
indeed it was working fine yesterday :/ sysadmin, any change in the api ?
Priority: Normal => HighAssignee: bugsquad => sysadmin-bugsSeverity: normal => major
CC: (none) => mageia-webteam
Release 2 has been added to api now. Can you try again ?
CC: (none) => boklm
Unfortunately I needed to start the upgrade and the upgrade worked once I used the proper switch/option, so I started the upgrade process. I'd rather not take a chance and quit the process. I'm on package 1374 of 2210. After looking at Manuel's post he may have missed that I used the wrong switch/option when I ran it initially (I spelled out the whole word "distribution"). I'm just reporting that the program doesn't provide an error and provides a misleading output when the wrong switches/options are used. I had a look at the mgaapplet-upgrade-helper script and it just looks like there is no check for invalid switches/options. Thank you, Jeff
My bad, it seems the option was changed since 2010.2 sorry :/ http://svnweb.mageia.org/soft/mgaonline/trunk/mgaapplet-upgrade-helper?revision=4158&view=markup 48 $::rpmdrake_options{$1}[0] = $2; 49 } elsif ($opt =~ /--new_distro_version=(.*)/) { 50 $new_distro_version = $1; with mgaapplet-upgrade-helper --new_distro_version=2 it works fine /me change the wiki
ok sorry all
Keywords: (none) => Junior_jobPriority: High => NormalCC: mageia-webteam => thierry.vignaudAssignee: sysadmin-bugs => bugsquadSummary: mgaapplet-upgrade-helper --new_distribution_version=2 no upgrade or error => check the option of mgaapplet-upgrade-helper before the launchSource RPM: (none) => mgaonlineSeverity: major => enhancement
What are you saying? The --new_distro_version option never changed and is named this since its introduction in 2008
yes sorry, I was wrong at any point on this bug...
Closing then
Status: NEW => RESOLVEDResolution: (none) => INVALID
I still think there is a problem because the script will run without checking for required arguments. I did not supply "new_distro_version" and the script still ran like I did and gave me a congratulations message. Also, we should probably fix the spelling of successful. --Jeff
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
You're not supposed to run it anyway. Mgapplet is the one that starts it.
There are instructions for running it manually in the Release Notes, which I freely admit I screwed up. If we never provided instructions on how to run the program manually, then I could see the argument for not checking the arguments. TBH, I would add argument checking anyway because it shouldn't be too much work and the program isn't time critical. Providing some documentation on the script would also be helpful, even if it's just with the "--help" argument. --Jeff
Version: 1 => CauldronWhiteboard: (none) => MGA2TOO
CC: boklm => (none)
CC: (none) => doktor5000
Assigning to tv who, I believe, is the maintainer for mgaonline. Are you? If so, please update the maintainers database.
Assignee: bugsquad => thierry.vignaud
CC: (none) => marja11Assignee: thierry.vignaud => mageiatools