Mailinglist Archive: opensuse-bugs (7277 mails)

< Previous Next >
[Bug 483648] Yast2 Online Update and Software Management use different verify system logic
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 12 Mar 2009 07:09:51 -0600 (MDT)
  • Message-id: <20090312130951.9255CCC703@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=483648

User ma@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=483648#c6


Michael Andres <ma@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |lslezak@xxxxxxxxxx
AssignedTo|zypp-maintainers@xxxxxxxxxx |jsuchome@xxxxxxxxxx
|o.novell.com |




--- Comment #6 from Michael Andres <ma@xxxxxxxxxx> 2009-03-12 07:09:50 MST ---
Comparing 'sw_single' and 'online_update' in y2log I see both using the same
set of 157 AutoSoftLocks when loading the pool.

But when it comes to solving, I see that most packages from openSUSE_11.1 and
Mirrored_updates repository lost their SoftLock. Actually it looks like the
best candidate of each package loses it's weak lock. I guess this is due to:

clients/online_update_select.ycp:69 Pkg Builtin called: PkgApplReset

./src/Package.cc: if (s) s->theObj().status().resetTransact(level);


I don't know why Pkg(Appl)Reset is needed, but it damages the users weak locks.
Maybe online_update can use SaveState/RestoreState to discard it's changes?

--
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.

< Previous Next >
References