Stanislav Visnovsky wrote:
Dňa Monday 25 February 2008 18:00:34 Michael Andres ste napísal:
As people are encouraged to use 'zypper dup', we get some reports which describe problems arising from the fact that we update the update stack in the running system.
After installing the new libzypp, zypper continues the transaction and is still using the old lib.
While the new libzypp converts and removes obsoltete locations (like the cache store or the obsolete sql databases) in it's post install script, the zypper running still tries to access these locations.
Maybe zypper should check whether the update stack needs an update, and handle this specially.
Yes, good point. I also think the correct way to upgrade the system is
'zypper in zypper' 'zypper dup'
The first command should make sure the proper libzypp is installed as well. In reality, the first command will install a complete software mgmt stack including YaST base packages, as they are tied to the particular version of libzypp. So, this works nicely IMO.
The question is whether to handle this from inside the dup command automatically, or to stick with just advising people to do the above. It should not be too hard to check if there is an update to libzypp and print "do 'zypper in zypper' first" message at least. j. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org