Update fail

[Brotherred]

I just restarted in an upgrade from MDV 2010 x86_64 and I can not finish do to this error:

Code: Select all

/usr/bin/perl: symbol lookup error: /usr/lib/perl5/vendor_perl/5.14.0/x86_64-linux-thread-multi/auto/URPM/URPM.so: undefined symbol: gzopen64

I simply restarted after installing glibc.

Please help,
Regards

[jkerr82508]

/usr/lib/perl5/vendor_perl/5.14.0/

Are you trying to upgrade to Cauldron?

Perl 5.14 is not available in Mageia 1, nor, so far as I know, in Mandriva 2010.

Jim

[Brotherred]

Yes I think so, Cauldron is Mageia 1? Then yes. As for the versions of specific libraries I do not know I do know that my upgrade from Mandriva failed. If I thought it were a issues with library versions I could fix that but I am sorta stuck between the two distros and need not to be.


Regards

[Akien]

No, Cauldron is the development release, which will become Mageia 2. So it is an unstable release, where big changes happen (like for now we are upgrading GNOME to version 3.02, and many packages need to be updated, so for now GNOME is kinda broken :p).

I don't know how you could update to Cauldron, though.

[Brotherred]

I think not then. So any ideas on how I can back out or else and more preferably continue with this upgrade?

[Akien]

Well, Mageia 1 has perl 5.12.3 and Mandriva 2010.2 has perl 5.10.1 so it's highly probable that you are in Cauldron...
Could you give us the output of the following command?

Code: Select all

cat /etc/release

And if you are effectively in Cauldron, could you explain how you proceeded to upgrade from Mandriva 2010 to Mageia?

[ahmad]

Backing out to Mageia 1 after updating to perl-5.14.0 will probably be too much hassle and trouble-prone... I suggest you back up your important files (and /etc, since it contains most of the configuration files), and do a clean install of Mageia.

[Brotherred]

Mandriva Linux release 2010.2 (Official) for x86_64

I choose to use urpmi to upgrade but I forgot to put in this command: # urpmi --replacefiles --auto-update --auto

I did the normal urpmi --auto-update and realized it was wrong as soon as I did it.

[ahmad]

Mandriva Linux release 2010.2 (Official) for x86_64

I choose to use urpmi to upgrade but I forgot to put in this command: # urpmi --replacefiles --auto-update --auto

I did the normal urpmi --auto-update and realized it was wrong as soon as I did it.

But that doesn't explain how you got Cauldron repos instead of Mageia 1 repos.

You can check what repos were added using:
urpmq --list-url

[Brotherred]

urpmq --list-url
Core Release http://mageia.webconquest.com/distrib/c ... re/release
Core Release Debug
Core Updates http://mageia.webconquest.com/distrib/c ... re/updates
Core Updates Debug
Core Updates Testing
Core Updates Testing Debug
Core Backports
Core Backports Debug
Core Backports Testing
Core Backports Testing Debug
Nonfree Release
Nonfree Release Debug
Nonfree Updates
Nonfree Updates Debug
Nonfree Updates Testing
Nonfree Updates Testing Debug
Nonfree Backports
Nonfree Backports Debug
Nonfree Backports Testing
Nonfree Backports Testing Debug
Tainted Release
Tainted Release Debug
Tainted Updates
Tainted Updates Debug
Tainted Updates Testing
Tainted Updates Testing Debug
Tainted Backports
Tainted Backports Debug
Tainted Backports Testing
Tainted Backports Testing Debug
Core 32bit Release http://mageia.webconquest.com/distrib/c ... re/release
Core 32bit Release Debug
Core 32bit Updates http://mageia.webconquest.com/distrib/c ... re/updates
Core 32bit Updates Debug
Core 32bit Updates Testing
Core 32bit Updates Testing Debug
Core 32bit Backports
Core 32bit Backports Debug
Core 32bit Backports Testing
Core 32bit Backports Testing Debug
[root@localhost brotherred]#

[Akien]

Well, you have indeed the Cauldron repositories (hence the "cauldron" in the URLs). I suppose you mistook Cauldron for Mageia 1 when you added the repositories, but I think there's no way back :/
I suppose ahmad is right:

Backing out to Mageia 1 after updating to perl-5.14.0 will probably be too much hassle and trouble-prone... I suggest you back up your important files (and /etc, since it contains most of the configuration files), and do a clean install of Mageia.

[Brotherred]

yeah I see that now that I clicked the link in my own post. Other than that I did not know. Conceding defeat and downloading now.

[Akien]

It could be useful to explain somewhere on Mageia's website what is Cauldron, for it seems plausible to imagine that Cauldron is the code name for Mageia 1. Though I don't know where the right place to talk about it would be.

[Brotherred]

Yeah I dunno anything. I know I have a cd to burn and that I choose the urpmi option and from there it "seemed" straight forward minus my hiccup that I mentioned about not doing --replacefiles. I can not conceive or remember any option for Cauldron or anything else. As far as I am concerned it should have just worked as described in the wiki but did not. But I knew the risks and it goes with the territory. I thank the devs for all of their hard work.

Regards.

[Brotherred]

Well guys I think this is where I say it has been real but it is a total fail for me on this box. I believe the MD5 was good but am not sure of how to confirm. I know the LIVE option on the cd would not boot. Here is a link to my curent computer make and model.

http://tinyurl.com/3qtwm2c


Regards

[Brotherred]

I just burned a Mandriva CD because I could not find my old one and got the exact same errors in booting it as I did with the Magiea CD. I know not to trust that burner with ISO's anymore.

[ahmad]

If your machine supports booting from USB sticks, you can dump the ISO on a usb stick, either using mandriva-seed (grab it from any Mandriva mirror), or plain dd http://www.mageia.org/wiki/doku.php?id= ... _usb_stick
(just be careful when using dd).

[Brotherred]

Thats cool. I used a external CD ROM because some how that burns better than the internal that is not labeled as a writer but does burn CDs.

I am already seeing the difference between the basically dead Mandriva and lively Magiea. Though I am now remembering how Firefox developers can lag in updating their extensions.

Regards all.

[ahmad]

Thats cool. I used a external CD ROM because some how that burns better than the internal that is not labeled as a writer but does burn CDs.

I am already seeing the difference between the basically dead Mandriva and lively Magiea. Though I am now remembering how Firefox developers can lag in updating their extensions.

Regards all.

You can workaround the Firefox addons compatibility issues, either:
- By using this addon https://addons.mozilla.org/en-US/firefo ... -reporter/ OR
- Editing the Firefox config manually: http://kb.mozillazine.org/Extensions.checkCompatibility