How to launch mgaonline GUI?

[tleedavidson]

The "Migrate from Mandriva Linux" (http://www.mageia.org/en/1/migrate/) page, which by the way I was able to find only via a Google search, under the "Upgrading inline" section says:

"So, the package has been installed? Good, let's move on, pick either a) or b) below:

a) Upgrading inline, using mgaonline (GUI)

a) Upgrading inline, using mgaonline (GUI)"

Then it shows an image of the launched update utility. But ... there is no instruction as to how to launch the mgaonline GUI update utility. How is this done?

An 'rpm -qa|grep mgaonline' shows that it is installed, but neither 'which' nor 'locate' find it.

Please tell me, how is this launched?

[Ken-Bergen]

Patients my friend. Mageia2 won't be released until May so there's nothing to upgrade to now.

[tleedavidson]

I am not trying to upgrade. I am not using Mageia1.

I am using Mandriva and trying to migrate from Mandriva to Mageia as is given as the title of the URL page I referenced:
"Migrate from Mandriva Linux"

I'm going to assume that it is not necessary for me to reiterate my question.

Thanks.

[Ken-Bergen]

Oops.
Have you tried logging out then back in to see if it launches?

[doktor5000]

You may want to check your /etc/sysconfig/mgaapplet for the initial delay, and if maybe you have disabled distribution upgrade check.
By default it will display 5 minutes after login, and will check for distribution upgrades when it runs.

BTW, the executable is called mgaapplet

[tleedavidson]

No, Ben, I did not log out and then back in to see if it launches. The "Migrate" instructions do not at all indicate that it should launch automatically. (It seems to me as though they should.) Hence, my query as to how to launch it thinking that it needed to be done manually.

Doktor, my /etc/sysconfig/mgaapplet has, not in order:
UPDATE_FREQUENCY=10800
DO_NOT_ASK_FOR_DISTRO_UPGRADE=false
FIRST_CHECK_DELAY=300000
Yes, that is three hundred thousand. And that is in seconds right? In other words then, 5000 minutes or over 83 hours before it first checks for updates. Or is that in microseconds?

It actually did not take 83 hours for the system to alert me that updates were available. It was probably on the default three-hour interval; or a five-minute delay -- I don't recall. A new icon appeared in the system tray, and I clicked on it to see what it was. It launched and informed me that Firefox needed to be updated. Just Firefox ... that's it. And so my sneaking suspicion, that 'mgaonline' was to have replaced the mandriva update utility, was shown, as it seemed, to be false.

On the "Migrate" page, the first sentence in the second paragraph in the Upgrading inline section says:
"This can be done either using the graphical mgaonline tool or the command-line urpmi."

The different font on both "mgaonline" and "urpmi" logically indicates that they are both application names since "urpmi" is an application name. So now rhetorically speaking, why is it referred to as "mgaonline" if it is really "mgaapplet"? And it is indeed "mgaapplet" -- 'which' found it no problem in /usr/bin.

Thank you both for your responses and guidance.

I'm not sure whether or not the mgaonline (mgaapplet) RPM is in need of fixing since it did not inform me of any new distribution. But I do think the migrate instructions could and should be more clear about what it is, what it is supposed to do and how, it's real name, and that it should launch automatically (& what to do if it does not). So ... how do I sign up to volunteer?

Lee

[doktor5000]

Well, the Migrate page definitely lacks some details reagarding mgaonline/mgaapplet, that is true.

FWIW, here's my configuration file, which has comments, which explains your question:

Code: Select all

[doktor5000@mageia1 ~]$ cat /etc/sysconfig/mgaapplet
# Update frequency (in seconds) [default is 3 hours]:
UPDATE_FREQUENCY=10800

# Initial check will be delayed by (default to 5 minutes):
FIRST_CHECK_DELAY=300000

# Globally enable or disable check for new distribution
# (in order to offer live distro upgrade):
# (default is "false", meaning check will be done)
DO_NOT_ASK_FOR_DISTRO_UPGRADE=false

Out of curiosity, you sucessfully followed the first step on the Migrate page for inline upgrade,
that is to install the Mageia version of it? http://www.mageia.org/en/1/migrate/#inline

[tleedavidson]

My /etc/sysconfig/mgaapplet config file is exactly the same as yours. So that "300000" is milliseconds.

Yes, I successfully followed the first step on the Migrate page for inline upgrade, namely, download and install the mgaonline RPM. I thought I made that evident in my first post

An 'rpm -qa|grep mgaonline' shows that it is installed

but looking back I can see how that may not have been clear. urpmq told me no such package was available, and I assume this is because it was querying the Mandriva repositories.

Perhaps installation of the mgaonline RPM should update the repositories as well.

[doktor5000]

Ahh, sorry, probably overlooked that bit.
Well, you could try to run mgaapplet-upgrade-helper, which will remove all your repositories, and the Mageia ones and check for an upgrade.
But i don't know if that's enough for the full upgrade. In any case, you could always use urpmi to upgrade inline.

BTW, is there anything in ~/.MdkOnline (or was it ~/.MdvOnline? don't remember that one)?

[tleedavidson]

Well I'm not sure I can mark this as SOLVED since I never got the mgaonline (GUI) utility to effect an upgrade for me.; though I did learn how it is to be launched. I did not even bother trying to run mgaapplet-upgrade-helper, because it seems to me that if that were necessary, it should be in the instructions on the "migrate" page. I suppose I should have just to see if it worked so that perhaps the instructions could be corrected or updated for the benefit of those that might follow. But I guess my motivation for that was diminished by the fact that my mention of the "migrate" page needing attention gained agreement from only one forum member and, as far as I know, no one in the Documentation group.

I ended up doing the migration via option b) Upgrading inline, using urpmi (CLI)

It appears to have worked superbly. No glitches, no hiccups, no headaches.

And BTW, Doktor, 'ls -a' shows nothing in ~/.MdkOnline other than the two directory "dot" files.

Thanks for all your help. I am now a new Mageia user!

Regards,
Lee

[doktor5000]

I did not even bother trying to run mgaapplet-upgrade-helper, because it seems to me that if that were necessary, it should be in the instructions on the "migrate" page. I suppose I should have just to see if it worked so that perhaps the instructions could be corrected or updated for the benefit of those that might follow. But I guess my motivation for that was diminished by the fact that my mention of the "migrate" page needing attention gained agreement from only one forum member and, as far as I know, no one in the Documentation group.

Well, the Migrate page definitely lacks some details reagarding mgaonline/mgaapplet, that is true.

FWIW, im a documentation team member, and as quoted above, it should definitely be improved, as you pointed out what is lacking. I'll see who i can poke about this

[tleedavidson]

Doktor, you were the forum member I referred to as agreeing with me. Obviously I was not aware that you are also a Doc team member.

And as I indicated earlier in this topic, I am willing to help; just don't know exactly where to start.

[doktor5000]

For reference, i've reported this as https://bugs.mageia.org/show_bug.cgi?id=4555
For the next time, you could try to look at https://wiki.mageia.org/en/How_to_report_a_bug_properly

[tleedavidson]

Really? I didn't realize that something like that might be considered a bug. I thought bug reporting was for software. How to report a bug properly certainly gives the impression that bugs occur only in software.

But I will keep that in mind for "next time." Thank you.

EDIT/UPDATE: I have commented on the "bug" report and indicated that I will try to come up with a "patch" in a couple days when I have a bit more time.

[doktor5000]

Really? I didn't realize that something like that might be considered a bug. I thought bug reporting was for software. How to report a bug properly certainly gives the impression that bugs occur only in software.

Meh, you just pointed out another documentation bug to me
Bugs can be everywhere, in software, in hardware, in the persons maintaining any of those, even in one's food (pun intended)
So basically if there's a reproducable problem, be it documentation, translation, artwork, the websites or infrastructure,
or anything else you can think of, it can be reported as a bug. Also package requests are bugs, to give some examples.

About that patch, maybe let's first discuss what should be changed on the migrate page regarding mgaapplet,
please do so in the bug. Just post your proposal there, what should be added (but please don't copy&paste
the rest of the migrate page there ) and then we'll see ...

[tleedavidson]

Gotcha. I got an email from Oliver Burger saying, "Just write here what you think should be on that page." So the discussion is open.