[zypp-devel] zypper dup shortcoming
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
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. Stano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
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
Dňa Tuesday 26 February 2008 17:59:32 Jan Kupec ste napísal:
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.
If this is possible, yes, would be good. I cannot imagine running the old zypper against new libzypp ;-) Stano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Am Mittwoch 27 Februar 2008 schrieb Stanislav Visnovsky:
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.
If this is possible, yes, would be good. I cannot imagine running the old zypper against new libzypp ;-)
Please don't confuse "the old zypper" with every daily Factory dup. So I would veto an extra caring for zypper. This could be done though if the product version changes. But then you might ask if we do not put too much effort into the edge :) Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
* Jan Kupec
The question is whether to handle this from inside the dup command automatically, or to stick with just advising people to do the above.
If it can be handled automatically, it should. Even experienced users tend to forget ;-)
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.
We might extend this by flagging all packages belonging to the 'update stack' with a special 'provides: update-stack'. Then zypper (resp. YaST) only has to check if packages scheduled for installation provide 'update-stack'. This would be more generic and flexible than checking for specific package names. Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (5)
-
Jan Kupec -
Klaus Kaempf -
Michael Andres -
Stanislav Visnovsky -
Stephan Kulow