Mageia 3 (Cauldron) instead of Mageia 2 after upgrade

[leif]

After a lot of troubles after the upgrade, my computer finally boots. There are still a lot of problems. One major issue is that the OS report itself as Mageia 3 (Cauldron) instead of Mageia 2. When I look at the installed rpms, at lot of them are mga3. I have no idea why this has happened. I certainly never selected Cauldron.

Is there a way to repair my installation?

[doktor5000]

Please give some details. How did you do the upgrade?
If there are many mga3 packages already, i can only give you the same answer as in viewtopic.php?p=19835#p19835

Chances are a big pile of cauldron packages has already been installed on your system.
Depending on the number and how firm you're in a terminal, it's probably easier, faster and more convenient to reinstall Mageia 2 but keep your /home.

[leif]

I originally upgraded with:
mgaapplet-upgrade-helper --new_distro_version=2

This left me with a system that did not boot due to lilo issues. In an attempt to rescue my installation, I used the installation DVD to upgrade to Mageia 2. During the upgrade, I was asked if I would like to configure additional installation sources. I think it was here it happened. The source I selected probably contained Cauldron rpms instead of Mageia 2 rpms as expected.

[doktor5000]

Well, probably the best thing would be to reinstall keeping your /home, and maybe creating a new user where you can migrate your old settings to later after the machine is working. This is the most clean way, and this is what i'm doing normally. It's also the most hassle-free overall IMHO.

[lxdragon]

I ran into the same problem. I did a CLI upgrade which did not go well, then I tried to upgrade with the DVD. When the DVD upgrade finished, I thought everything worked, but then realized I was on Cauldron. Maybe some repos are fubar?

Chris

[doktor5000]

How exactly did you do the CLI upgrade, and did you maybe add repositories during installation from DVD? Please be more specific ...

[lxdragon]

For the CLI upgrade, I followed the directions on the upgrade page. The reason it failed was my own fault, I had forgotten to clear out a bunch of old kernels in the /boot partition, and it filled up.

For the DVD install, I did add the non-free and experimental repos because I wasn't sure which one I needed for my Nvidia driver.

I don't remember any other details, I just mentioned that it happened to me in case there was a problem with a repo that should be investigated.

[doktor5000]

For the DVD install, I did add the non-free and experimental repos because I wasn't sure which one I needed for my Nvidia driver.

I don't remember any other details, I just mentioned that it happened to me in case there was a problem with a repo that should be investigated.

Experimental? Maybe you mean tainted?

As for the general problem description (adding one or more repos during installation and than ending with cualdron repos) i've already heard that several times, but so far noone could provide more details so we can take a look what went wrong. Do you still have that broken DVD/cauldron install? Please open up a bug for that issue and attach your /root/drakx/report.bug.gz from that installation so we can investigate and possible fix this.
https://wiki.mageia.org/en/How_to_report_a_bug_properly

[lxdragon]

Unfortunately, I just re-installed from the DVD using "install" instead of "upgrade". Although even this method wanted to install Cauldron again. I had added two mirrors in the US, kernel.org and ibiblio, and during the install, I noticed the kernel with "mga3" in it, so I aborted, formatted the /boot and / partitions, and started over. The second time, I did not add any mirrors during the install, and it seemed to work OK. Although the version in /etc shows up as "2 4 cauldron", at least all the packages are mga2 and I don't have the Cauldron blank text bug anymore.

[Ken-Bergen]

Could you please give us the exact name of the iso you used to burn the DVD or a link to it so that we can test?

[lxdragon]

I can get you the iso filename next Monday (I downloaded it at work and I'm on holiday this week). One additional note, I just checked the mageia-release file in /etc, and it looks good: "Mageia release 2 (Official) for i586".

Thanks

[lxdragon]

The iso image is Mageia-2-i586-DVD.iso and I got it from kernel.org or ibiblio.

[leif]

It has happened to me AGAIN!

One of my computers stopped working correctly a week ago and since the motherboard and CPU were old, I decided to replace them. I thought that it would be a good idea to run an upgrade of my Mageia 2 installation with the installation DVD, since there were hardware changes. During the upgrade, I configured an FTP source too. This was a very bad idea since it obviously found a Cauldron source instead of a Mageia 2 source. The upgrade did of course not succeed correctly and I am now stuck with a corrupt Mageia 2/Mageia 3 installation.

[leuhmanu]

without real details we can't help you.

I testesd quickly mgaapplet-upgrade-helper --new_distro_version=2 and it add perfectly the mageia 2 repositories.

[leif]

Well, during the installation, I was asked for additional sources. As I recall, I selected FTP-source. Then I had to configure a network adapter. After some time, I got the message that it was configured but could not be tested or did not work or something similar. That usually happens, probably another bug, but I don't think it is relevant here. In anyway, I was then presented a list of sources. Since I live in Sweden, I selected ftp://ftp.sunet.se as my source. Maybe the problem is here. Perhaps some repositories are misconfigured and will provide Cauldron instead?

[doktor5000]

No, i recall quite some people had this problem since Mageia 2 was released, but only when adding repos during the installation.

[Ken-Bergen]

I'm unable to reproduce it now but twice installing Mageia1 from a USB key I ended up with Mageia3.

The problem appears to be that the installer even though initiated from the USB key actually installed from the Mageia-Alpha-3 DVD in my optical drive.

This may or may not relate to the problems others are having.