Bug 619316

Summary: Yast2 Wagon aborts immediately after "renew update stack" completes
Product: [openSUSE] openSUSE 11.3 Reporter: Greg Freemyer <Greg.Freemyer>
Component: YaST2Assignee: Martin Vidner <mvidner>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: jreidinger
Version: RC 2   
Target Milestone: ---   
Hardware: All   
OS: openSUSE 11.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Greg Freemyer 2010-07-01 21:07:41 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9

This may relate to bugzilla #613820

This time I started with 11.2 machine with YOU recently run.  No other repositories were in use but the 3 official repos.

I disabled the 3 11.2 repos and added the factory repos:

http://download.opensuse.org/factory/repo/oss/
http://download.opensuse.org/factory/repo/non-oss/

I then launched "yast2 wagon" from the command line.

wagon itself renewed the "update stack".  Effectively pulling down the factory components used by wagon.  About 1 GB of files were pulled by that update.

At the end of the update stack renewal process, I got

==
# yast2 wagon
Error loading language plugin /usr/lib64/YaST2/plugin/libpy2lang_perl.so: libperl.so: cannot open shared object file: No such file or directory
Error while creating client module wagon
#
==

Obviously only the update stack was updated to RC2

Looks like a missing dependency to me.


Reproducible: Didn't try

Steps to Reproduce:
1.
2.
3.


Expected Results:  
An upgraded 11.3 RC2
Comment 1 Xiao Yu Yang 2010-07-02 01:10:23 UTC 
Please attach y2logs,if you're in doubt follow up http://en.opensuse.org/Bugs/YaST 
Thanks!
Comment 2 Greg Freemyer 2010-07-02 03:51:33 UTC 
I can get that in the morning (12 hours from now).

But what do I need to get you so you can analyze wagon's "renew upgrade stack" process.

That caused hundreds of packages to be pulled.  Is that list in the yast logs?

I have to believe the bug is in the selection of those packages and/or the dependencies within that collection.

ie. Wagon worked previous to it internally running "renew upgrade stack", but after it finished it was not able to exec itself.  ie. I'm pretty sure that's what it does: update its own packages and its dependencies, then re-exec itself.  Its the re-exec I'm confident is failing due to the missing lib.

In fact, if I now exec yast2, it works, but as soon as I select "software management", I get the same exact perl error.

Clearly my upgraded packages were left in a state that doesn't allow yast to be fully functional.
Comment 4 Stanislav Visnovsky 2010-07-02 07:46:16 UTC 
Definitely looks like dup of #613820
Comment 5 Lukas Ocilka 2010-07-02 08:29:15 UTC 
Looks like a dependency issue.
Comment 6 Josef Reidinger 2011-06-21 15:27:42 UTC 
I agree with duplicate. It is perl dependency problem

*** This bug has been marked as a duplicate of bug 613820 ***