https://bugzilla.novell.com/show_bug.cgi?id=384254 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=384254#c35 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|ma@novell.com | --- Comment #35 from Ján Kupec <jkupec@novell.com> 2008-05-14 04:16:09 MST --- First, there is (AFAIK) no difference between zypper dist-upgrade/update -t package/install/verify when it comes to installing rpms. It just calls rpm to install or update the packages you see in summary. That's why nscd update fails also with zypper install (c#22).
Do we run into trouble if we set YAST_IS_RUNNING to "instsys" for the
Yes:
`zypper dup' command? In other words does zypper execute the rpm setup scripts (%pre, %post, %preun, %postun, and any %trigger) as YasT does is on update case? Compare with the rpm macros found in
No, zypper does not do any of this nor does it any other additional work yast does when this variable is used. This is most probably not easily doable (but may be wanted in the future - a FATE request?) OTOH package scripts should be able to function also without such variable, see below.
On the other hand, does zypper and/or libzypper use own environment variables in case of `dup' which could be checked by insserv?
No, zypper/libzypp just calls rpm, it does not set any env variables. You can think of this situation like running the update with plain rpm (look at zypper.log to see how exactly was rpm invoked for each package) on a running system. If it fails like said in this report (it should), it should be fixed to work with plain rpm. Then it will work with zypper, too. -- 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.