http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c1 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |Greg.Freemyer@gmail.com Severity|Major |Critical --- Comment #1 from Andreas Jaeger 2010-06-15 07:48:47 UTC --- Segfault -> Critical according to our bugzilla guidelines. Could you add the YaST log files, please? See http://en.opensuse.org/Bugs/YaST for details. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c3 Greg Freemyer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Greg.Freemyer@gmail.com | --- Comment #3 from Greg Freemyer 2010-06-15 13:41:46 UTC --- Created an attachment (id=369249) --> (http://bugzilla.novell.com/attachment.cgi?id=369249) gzip'ed yast2 log directory Hope this is sufficient -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c4 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juhliarik@novell.com AssignedTo|yast2-maintainers@suse.de |locilka@novell.com --- Comment #4 from Jozef Uhliarik 2010-06-21 08:00:19 UTC --- I am not sure if it was good idea start update of OS with upgrade the yast components to milestone 7 and next to start yast2-wagon for updating OS. Lukas you are expert for using yast2-wagon. The bugs describe troubles with using yast2-wagon for updating OS. I think that problem is broken YaST by updating his components before starting yast2-wagon but maybe it is correct way how to use it. Please check it. I vote for closing bugs (INVALID) because updating system was broken by user (updating YaST to milestone 7) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c6 --- Comment #6 from Greg Freemyer 2010-06-21 12:54:59 UTC --- (In reply to comment #4)

I am not sure if it was good idea start update of OS with upgrade the yast components to milestone 7 and next to start yast2-wagon for updating OS.

Lukas you are expert for using yast2-wagon. The bugs describe troubles with using yast2-wagon for updating OS. I think that problem is broken YaST by updating his components before starting yast2-wagon but maybe it is correct way how to use it.

Please check it.

I vote for closing bugs (INVALID) because updating system was broken by user (updating YaST to milestone 7)

You misunderstood how the upgrade of yast components occurred. I was at 11.3 M3 when I entered "yast2 wagon" at the cli. At that point my yast components were upgraded automatically. I assume wagon itself has logic to upgrade itself to the latest available release prior to beginning the full system upgrade. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c8 --- Comment #8 from Greg Freemyer 2010-06-29 18:51:30 UTC --- Given that RC2 is soon for this world, is there any reason for me NOT to go ahead and upgrade my test laptop to RC1 via zypper dup. And then when RC2 comes out attempt yast2 wagon again and report the results of that here? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c10 --- Comment #10 from Greg Freemyer 2010-07-01 21:25:57 UTC --- I just tried yast-wagon straight from OS 11.2 It also performed "renew upgrade stack" then aborted, but no segfault this time. I created https://bugzilla.novell.com/show_bug.cgi?id=619316 since it seems different enough to be a different bug. But the core of it is: === 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 === Since the entire update stack was first pulled in from RC2 by yast-wagon, this one looks like a simple missing dependency to me. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c12 Stanislav Visnovsky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |visnov@novell.com --- Comment #12 from Stanislav Visnovsky 2010-07-02 07:47:40 UTC --- Fix in 11.3 should be enough as the missing dependency should fix the 'upgrade stack' step. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c14 --- Comment #14 from Greg Freemyer 2010-07-02 12:49:10 UTC --- (In reply to comment #11)

I guess the problem is caused wrong (unversioned) perl dependency. I have fixed that in yast2-perl-bindings-2.19.0 in 11.3, but in 11.2 it's not fixed.

The workaround should be manually updating yast2-perl-bindings to version >= 2.19.0.

Martin, any idea?

(I'm not worried about a workaround. I'm testing Wagon in hopes it will work for 11.2 => 11.3 by the community. I think its a great tool when it works and should be the "user friendly upgrade tool" pushed in the announcement. For me, I can always zypper dup and get upgraded.) ==> testing your fix For the machine that started at 11.2 + YOU, I want to revert back to 11.2 and retry the upgrade via wagon with your fix in. After I put the repos back to 11.2, what zypper command do I need to run to revert back to a vanilla 11.2 environment. After that, is your dependency fix already in the factory repo, or is there another repo I can use to test wagon? Or do I need to wait a while for your fix to hit factory? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c16 --- Comment #16 from Greg Freemyer 2010-07-02 15:19:36 UTC --- (In reply to comment #15)

So far I haven't been able to reproduce the bug. I used the RC2 DVD repository for the update, not Factory, and entered it only during wagon's run, not beforehand. I noticed that wagon did not update itself during the initial patch, probably because it is missing from the RC2 DVD.

I was exactly following the steps at http://en.opensuse.org/Wagon for 11.2 => 11.3 upgrade. Obviously I used the factory repos. Martin, if your attempt to upgrade from 11.2 to 11.3 via Wagon and the RC2 DVD did not cause several hundred packages to upgrade during the "Renew Upgrade Stack" phase, then I am not surprised you did not duplicate the bug. I'm fairly confident it is that "Renew Upgrade Stack" process that introduces the mis-versioned upgrade stack. Since factory may already have the new dependency, testing with the RC2 milestone repo would be the most reliable way to reproduce the issue. And then repeating the test with the real factory repo would be a good way to test it is resolved. That is once the fix gets fully into factory. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c18 --- Comment #18 from Greg Freemyer 2010-07-07 02:46:47 UTC --- I attempted the 11.2 => 11.3 factory upgrade today (ie. post RC2) It still fails, so I assume the dependency update hasn't made it to factory yet. I don't know when 11.3 final is, but if wagon is going to be usable for 11.2 => 11.3 upgrades it has to me in the main repo, not an update repo so time is running out to get this in and tested. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c20 --- Comment #20 from Arvin Schnell 2010-07-07 09:14:29 UTC --- A dependency for perl in yast2-storage was added April 9th: Requires: yast2-perl-bindings perl = %{perl_version} Is there still missing something? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c22 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@novell.com AssignedTo|mvidner@novell.com |locilka@novell.com --- Comment #22 from Martin Vidner 2010-07-07 14:36:11 CEST --- Yes, and it is worked around in the same way. The branched yast2-wagon now Conflicts: yast2-perl-bindings < 2.19.0 Conflicts: yast2-storage < 2.19.0 It has worked, once I manually changed the wagon version to confirm the vendor change (openSUSE -> home:mvidner). Now I wanted to submit the fix to Factory, but it turns out SVN contains lots of changes[1] which went only to SLE but not into openSUSE[2]. I let Lukas, the maintainer of the package, sort out the mess. 1] http://svn.opensuse.org/viewvc/yast/trunk/wagon/package/yast2-wagon.changes?revision=61324&view=markup 2] https://build.opensuse.org/package/view_file?file=yast2-wagon.changes&package=yast2-wagon&project=openSUSE%3AFactory -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |mvidner@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c25 --- Comment #25 from Greg Freemyer 2010-07-07 18:17:31 UTC --- I tested 2.18.1.1-8.1 from your test repo. I got past the "renew update stack" process and the real distro upgrade is in process. It will take a couple hours to finish, but it definitely looks to me like the 2 conflict lines fix this bug. Now if you can get those fixes into factory? And thanks for working on it. I get the impression not many openSUSE people even know yast2-wagon exists. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613820 http://bugzilla.novell.com/show_bug.cgi?id=613820#c27 --- Comment #27 from Greg Freemyer 2010-07-19 15:29:47 UTC --- Any chance we can get this into the update repo soon? It seems as simple as branching from 2.18.1-4.2 and adding the two conflicts statements and updating the version, then submitting to the online upgrade repo. ie. Conflicts: yast2-perl-bindings < 2.19.0 Conflicts: yast2-storage < 2.19.0 But, I've never been part of the online upgrade process, so maybe its more involved than I would guess. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=613820 https://bugzilla.novell.com/show_bug.cgi?id=613820#c29 --- Comment #29 from Josef Reidinger 2011-06-21 15:27:42 UTC --- *** Bug 619316 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=619316 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.