openSUSE 10.3 Updater error: Please help

[akarui.t...@gmail.com]

It started all in a sudden.
Toda (Novemver 16, 2007), when I started openSUSE 10.3, everything was
fine.
openSUSE updater application asked me to download some available
updates and I started the updater (as a root).
But it gave me error message as below:

"Can't launch zypp-checkpatches-wrapper helper program. Make sure
zypper package is installed and working."

According to the suggestion, I attempted to install "zypper" package
from YAST (Software->Software Management).
But, once I click on the "Software Management" icon, an "xmessage"
windows pop up with the following error message:

"Error loading language plugin /usr/lib/YaST2/plugin/
libpy2lang_perl.so: libzyppy.so.324: canot open shared object file: No
such file or directory No such client module sw_single

Run 'yast2 -h' for help on usage"

Note that, my openSUSE 10.3 is up-to-date, because I always install
the available updates everyday.

[rivenought]

Here is one fix from Dave Thorp via the SUSEforums.net and the Novell
Bugzilla. It worked for me, but I had to choose the 64-bit versions
of the packages instead of the 32-bit ones. I hope this helps.

Slightly clearer instructions that I've just posted on the bugzilla

Ok to solve (for anyone still desperate to get package management back)

Go to http://download.opensuse.org/distribution/.../oss/suse/i586/ and
pick up the following three packages and save them to their own folder
(all 3
packages in one folder)

http://download.opensuse.org/distribution/...26.2-2.i586.rpm (libzypp)
http://download.opensuse.org/distribution/....1-108.i586.rpm (boost)
http://download.opensuse.org/distribution/...8.23-7.i586.rpm (zypper)

Open a shell and su to root

cd to the folder you put them in

rpm -e boost-1.33.1-108.2 (which erases the wonderfully and thoroughly
tested
package that caused the mess)
rpm -ivh *.*

Right click on the opensuse updater and click check now and all should
be back
to normal

[russbucket]

rivenought wrote:

> (all 3
<snip>

>
> http://download.opensuse.org/distribution/...26.2-2.i586.rpm (libzypp)
> http://download.opensuse.org/distribution/....1-108.i586.rpm (boost)
> http://download.opensuse.org/distribution/...8.23-7.i586.rpm (zypper)
>
> Open a shell and su to root
>
> cd to the folder you put them in
>
> rpm -e boost-1.33.1-108.2 (which erases the wonderfully and thoroughly
> tested
> package that caused the mess)
> rpm -ivh *.*
>
> Right click on the opensuse updater and click check now and all should
> be back
> to normal

Did what you described above;

Had to delete the -doc and -devel rpms of boost before boost would delete.

After everything worked fine but I got the following message about
permissions:

rpm -ivh *.*
Preparing... ###########################################
[100%]
1:boost ########################################### [
33%]
2:libzypp ########################################### [
67%]
No sources to migrate.
3:zypper ###########################################
[100%]
Starting SuSEconfig, the SuSE Configuration Tool...
Running module permissions only
Reading /etc/sysconfig and updating the system...
Executing /sbin/conf.d/SuSEconfig.permissions...
Checking permissions and ownerships - using the permissions files
/etc/permissions
/etc/permissions.easy
/etc/permissions.d/mail-server
/etc/permissions.d/postfix
/etc/permissions.d/texlive
/etc/permissions.local
setting /usr/sbin/zypp-checkpatches-wrapper to root:root 4755. (wrong
permissions 0755)
Finished.

YaST appears to be working fine now. Did not do anything to fix permissions.

Thanks for posting this fix. I guarantee I will not install a fix for boost
until I'm sure it works.

Thanks again for your help!!!!!
--
Russ
Registered Linux user #441463

----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Paul J Gans]

This may do it. I've been a SUSE user since 7.2 but I may have
to say goodby. In the three weeks since my boxed set (I try
to support SUSE) arrived I've done nothing but patch bugs.

Any chance that SOMEBODY will box up (in an rpm or tar file
or whatever) the needed files to fix this fiasco and put
them on the main openSUSE site with clear instructions as
to what to do?

Probably not. That would be logical.

My thanks to the folks who both developed the fix and who
posted it here. Now if somebody would give me the proper
URL (I don't do SUSE arcana well) because clearly

http://download.opensuse.org/distribution/...26.2-2.i586.rpm

isn't a proper URL.

Anyone have any experience with PCLinuxOS?

--
--- Paul J. Gans

[akarui.t...@gmail.com]

On Nov 16, 9:48 pm, Paul J Gans <g...@panix.com> wrote:
> rivenought <rivenought.l...@aol.dude> wrote:

rivenought.like gave a solution. Thanks.
But the links are broken. Could you please the "correct" URLs so that
everyone could be benefited ?
Thanks in advance.

[akarui.t...@gmail.com]

Finally, I found the correct information from the buzilla.

/
************************************************************************************
------- Comment #5 From David Thorp 2007-11-16 14:55:29 MST -------

Ok to solve (for anyone still desperate to get package management
back)

Go to http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/

and
pick up the following three packages and save them to their own folder
(all 3
packages in one folder)

http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/libzypp-3.26.2-2.i586.rpm
http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/boost-1.33.1-108.i586.rpm
http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/zypper-0.8.23-7.i586.rpm

Open a shell and su to root

cd to the folder you put them in

rpm -e boost-1.33.1-108.2 (which erases the wonderfully and thoroughly
tested
package that caused the mess)
rpm -ivh *.*

Right click on the opensuse updater and click check now and all should
be back
to normal

*********************************************************************************************/

[rivenought]

<snip>

Sorry for the confusion, guys. Somehow in getting the info
copied/pasted/posted, the links got abbreviated. I had just fixed my
computer bare seconds previously and since I was still in red-alert
mode, I neglected to completely check the links I was posting. Those
links worked when I used them, but I may have used the Bugzilla links
and copied the SUSEforums.net post by the same extremely helpful guy,
David Thorp. Events were in somewhat of a blur for a while there.
After I was back up and running, my main thoughts at the time were the
importance of immediately posting some info on this newsgroup to help
those that might have begun to panic.

The above info is the same that seems to work for almost everyone.
There are several methods which will work, depending on your system.
If there are other instances of Boost installed, they must be removed
as well. As I already said, I had to change repositories to get the
64-bit versions. While in Konsole, I also got some odd messages about
permissions, but I clicked on through them, and everything seems to
work now. YaST is back to regular operation.

Once again, I am sorry for the broken links. I was just trying to be
helpful as quickly as possible and did not proofread. Hopefully,
everyone who was affected has been able to get back to normal.

[cart...@despammed.com]

On Nov 16, 9:48 pm, Paul J Gans <g...@panix.com> wrote:

> This may do it. I've been a SUSE user since 7.2 but I may have
> to say goodby. In the three weeks since my boxed set (I try
> to support SUSE) arrived I've done nothing but patch bugs.
>

<snip>

>
> Anyone have any experience with PCLinuxOS?

Yep, in my experience, the one thing it doesn't do well is recognize
dial-up modems, which is why I'm booting SuSE 10.0 as well as
PCLinuxOS. But most things just work from the default install. The
local users group I attend has standardized on PCLinuxOS.

Rick Carter

[Paul J Gans]

You are certainly forgiven. I didn't think that you purposefully
abbreviated the links. I've seen the /...<somefilename> notation
used on the SUSE bugzilla where, I guess, everybody knows the
right links.

You deserve thanks for letting us know that there is a fix
out there.

[Paul J Gans]

Thanks. I'd love to stay with openSUSE, but there is too
much breakage in what should be a mature distribution.

But I'm not going yet.

[Harald.M...@googlemail.com]

You will find a solution in Novell's bugzilla - bug 342394

https://bugzilla.novell.com/show_bug.cgi?id=342394

, which also handles this issue.

export ARCH=$(rpm -q --qf "%{ARCH}\n" aaa_base)
rpm -e boost-doc; rpm -e boost-devel; rpm -e boost;
rpm -Uvh \
http://download.opensuse.org/distribution/10.3/repo/oss/suse/$ARCH/libzypp-3.26.2-2.$ARCH.rpm
\
http://download.opensuse.org/distribution/10.3/repo/oss/suse/$ARCH/boost-1.33.1-108.$ARCH.rpm
\
http://download.opensuse.org/distribution/10.3/repo/oss/suse/$ARCH/zypper-0.8.23-7.$ARCH.rpm

Ignore errors on removal of boost-* you might not have all subpackages
installed.

[dsimm...@gmail.com]

On Nov 18, 2:40 am, Harald.Mueller...@googlemail.com wrote:

> You will find a solution in Novell's bugzilla - bug 342394

> , which also handles this issue.
>
> export ARCH=$(rpm -q --qf "%{ARCH}\n" aaa_base)
> rpm -e boost-doc; rpm -e boost-devel; rpm -e boost;

> rpm -Uvh \http://download.opensuse.org/distribution/10.3/repo/oss/suse/$ARCH/li...
> \http://download.opensuse.org/distribution/10.3/repo/oss/suse/$ARCH/bo...
> \http://download.opensuse.org/distribution/10.3/repo/oss/suse/$ARCH/zy...

>
> Ignore errors on removal of boost-* you might not have all subpackages
> installed.

Well....not exactly working on this end. I had to:

rpm -e --nodeps boost; rpm -e --nodeps zypper; rpm -e --nodeps libzypp

and then 'rpm -Uvh' the freshly downloaded *.rpm's.......then the
problems begin.

Once they're all (re)loaded.....and I do a 'Check for Updates' - it
finds that the libzypp and zypper rpm's are updated on the
'OpenSUSE-10.3-Updates' repository. It marks them as 'Mandatory' and
downloads/installs them first...then I have approx 60+ optional
installs that it fails on (like original issue)....arggg....I'm going
in circles.

The solution seems to be to remove the 'Enabled' from that (the 10.3-
updates one) repository (therefore removing it) and then do a 'Check
for Updates'....let it install the 60+ optional updates first

Then readd the OpenSUSE-10.30-Updates repository (which mandatory
updates the above two)...The system is still screwy/broke - in that
when I start bringing in other Repositories (like Packman) that have
updates - it goes back to the same action of not installing updates.

Help!?

[dsimm...@gmail.com]

On Dec 9, 9:15 pm, dsimmons...@gmail.com wrote:
> ...The system is still screwy/broke - in that
> when I start bringing in other Repositories (like Packman) that have
> updates - it goes back to the same action of not installing updates.

Ok...actually, I guess I shouldn't vilify the Packman group....it was
actually the VideoLan repository that has 4 updates that I can't seem
to install....but I believe it all goes back to the root issue....can
someone help clarify and provide a thorough and complete solution to
fixing the 'available updates' app

Thanks! - dave