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. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org