Mageia forum

At this moment, I am doing an upgrade from mageia 3 to mageia 4. I am doing this as an online upgrade, following the instruction here: https://wiki.mageia.org/en/Mageia_4_Release_Notes

But I am receiving a large number of packages labeled mga5, for instance, this one:

media/core/release/sharutils-4.14-1.mga5.x86_64.rpm

Why is this? Do I somehow have cauldron (or cooker...or whatever) packages coming in? Am I going to have an unstable system when I reboot?

yup. I clearly am getting cauldron. I see a few mga4 packages, but most are mga5. Also, kernel 3.13, KDE 4.12.

Well, this should be interesting.

I reviewed the install instructions, and what I did was copy/paste from the web page into the konsole, so what I did was issue this command:

urpmi.addmedia --distrib --mirrorlist http://mirrors.mageia.org/api/mageia.4.$ARCH.list

without making the x86-64 substitution for $ARCH (which is mentioned on the next line.

Well, urpmi.addmedia took it, but now I am getting cauldron packages. Would be better if the command bombed.

I use cauldron in a separate partition and I don't have any problem. I don't know what happened with the instructions

jiml8 wrote:urpmi.addmedia --distrib --mirrorlist http://mirrors.mageia.org/api/mageia.4.$ARCH.list

IIRC you need to escape the URL

Code: Select all

urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.4.$ARCH.list'

But still can't think of a reason why you'd gotten mga5 repos. Check e.g. http://mirrors.mageia.org/api/mageia.4.x86_64.list
What does /etc/product.id show (if it hasn't already been updated) ?

The distro identified itself as mageia 5, however the desktop was so badly broken that I quickly gave up and rolled back. Now I have the usual nightmare trying to get kmail working again.

I got tired of wrestling with kmail again to restore my emails again, so I decided to try rolling forward...again.

This time, after entering the command line properly, the upgrade went without a hitch. That is a bug; urpmi.addmedia should fail if the syntax is incorrect. Instead, it added the cauldron repos.

So I'm up and running in Mageia 4 now. There have been a couple of minor issues, which I worked out, and kmail seems to be a lot more stable (I hope, I hope, I hope...). Also, virtuoso seems to be working better.

The one issue that does bother me is that fusion-icon is crashing with a message "compizconfig - Error: Unable to find interface type 2 on...". This is most probably an upstream problem, though I might obtain the source and compile it here to see for sure if it is.

jiml8 wrote:That is a bug; urpmi.addmedia should fail if the syntax is incorrect. Instead, it added the cauldron repos.

Well, best report it.

jiml8,

I've researched "compizconfig - Error: Unable to find interface type 2 on..." to death! I've recompiled it and it is basically a bunch from scripts I guess. It is strange as fusion-icon is not a plain old binary.

Compiz is goofy too. I forget what all but one problem is when you maximize a window by double clicking the title bar and then do it again to resize it back to a window the title bar becomes disabled, that is, you can't even drag the windows with it. We should start a thread on it I guess but I had given up.

I forget what all but one problem is when you maximize a window by double clicking the title bar and then do it again to resize it back to a window the title bar becomes disabled, that is, you can't even drag the windows with it. We should start a thread on it I guess but I had given up.

I do not confirm that problem here; it works fine on my system when I do that.

As for fusion-icon, I did dig into it a bit. That program is a python program. Now, I don't speak python, but with the help of the search engines, I figured out how to use the python debugger, and traced the problem into how python handles threads (or subprocesses as they are called, apparently, in python). I traced the problem out of fusion-icon and into another library function.

Again, I don't speak python, but I tentatively conclude the issue has to do with the python installation in mga4. At this point, that is all I think I know about it and I may look into it more when I have time.

I had decided my title bar problem may be related to me ATI/AMD driver.

Not sure, but maybe we can start a Compiz thread and narrow it down. Yeah, Python, that is is.

I don't do Python either as you can tell. I did find that it said something was linked twice somewhere?

I'm look it over again and we'll get a thread going.