Hi,
To upgrade my system from 11.1 to 11.2, I followed he instructions at:
openSUSE Lizards » Updating in Place From openSUSE 11.1 to 11.2
However, it failed and now I am stuck with this error:
zypper: error while loading shared libraries: libaugeas.so.0 cannot open shared object file: No such file or directory
can someone please help me to get over this…
The steps taken were:
First disable all old repositories, either in YaST or with zypper using “zypper mr –all -d”.
[LIST=2]Then add the new repositories, in case of factory, you can do this via the following commands:
zypper ar -f http://download.opensuse.org/update/11.2/ "openSUSE 11.2 Updates"
zypper ar -f http://download.opensuse.org/factory/repo/oss/ "openSUSE Factory Oss"
zypper ar -f http://download.opensuse.org/factory/repo/non-oss/ "openSUSE Factory Non-Oss"
zypper ar -f http://download.opensuse.org/factory/repo/debug/ "openSUSE Factory Debug"
[/LIST]
[LIST=3]I run “zypper refresh” to get the local metadata and repo contents[/LIST]
[LIST=4]I upgraded the package stack to the new version with “zypper in zypper”[/LIST]
[LIST=5]I updated the rest of the system with “zypper dup”[/LIST]
After this system crashed and i am left with the terminal and the error I mentioned in post#1
One question. When you say you added OSS and NON-OSS Factory - Is that what you mean? Or do you mean 11.2?
If Factory - Why?
Hi,
I’ve made step 1 more clear.
I don’t have reason why I did it. I simply followed the steps mentioned at opensuse->lizards post because everyone was able to use it.
But that was written whilst 11.2 was in development. I gave you the link for 11.2 final
Change your repos to 11.2 official release repos and see if you can force an update of zypper. You may have to manually download the zypper .rpm and install it with
rpm -Uvh *packagename --force --nodeps
Otherwise you may want to consider a fresh install, just keeping /home
I actually screwed my system when (1 month back) only that tut was available.
Anyhow, i installed the latest zypper but now its giving me error for libzypp.so
Also, if I try to use yast this is the error I am getting:
Can't locate Config.pm in @INC (@INC contains: /y2update/modules /root/.yast2/modules /usr/share/YaST2/modules /usr/lib/perl5/5.10.1/i586-linux-thread-multi /usr/lib/perl5/5.10.1 /usr/lib/perl5/site_perl/5.10.1/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.10.1 /usr/lib/perl5/vendor_perl/5.10.1/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.10.1 /usr/lib/perl5/vendor_perl .) at /usr/lib/perl5/5.10.1/diagnostics.pm line 195.
BEGIN failed--compilation aborted at /usr/lib/perl5/5.10.1/diagnostics.pm line 195.
Compilation failed in require at /usr/lib/perl5/vendor_perl/5.10.1/i586-linux-thread-multi/YaST/YCP.pm line 119.
BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.10.1/i586-linux-thread-multi/YaST/YCP.pm line 119.
Compilation failed in require at /usr/share/YaST2/modules/URLRecode.pm line 16.
BEGIN failed--compilation aborted at /usr/share/YaST2/modules/URLRecode.pm line 16.
Compilation failed in require.
BEGIN failed--compilation aborted.
e%@Loading /root/.kbd/.keymap_sv
Is there any way I can upgrade directlly from internet??
Are you implying that you can’t use or don’t have cd/dvd drive?
I’ve cd/dvd drive but since my system is half upgraded so I don’t see a point in downloading 700MB of live-CD and then upgrading the whole system again.
Let me know if that’s the only option.
P.S: I’ve a very slow internet cnx 192Kbps so even downloading 700MB will take half a day.
But you are kind of in a mess and honestly I think an install is the way to go. Net install is possible but it would not be wise if you have poor internet. And having a CD is more to fall back on, even better a dvd.
Factory is on 11.3 already!
I remember seeing some complaints on factory list about perl failing, so it seems you chose an unlucky moment to “upgrade(?)” to it.
To upgrade to 11.2, use 11.2 repos only! Recover your system via backup, or shrink your data partitions and free up an 8GB partition to clean install 11.2 into.
In Fate there is an entry suggesting automatic “Current” release, so you can automatically have the repo’s changed, or switch to “Factory” to be a pre-alpha tester guinea pig.