https://bugzilla.novell.com/show_bug.cgi?id=729796
https://bugzilla.novell.com/show_bug.cgi?id=729796#c11
Ruediger Oertel changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
CC| |ro@suse.com
InfoProvider|ro@suse.com |
--- Comment #11 from Ruediger Oertel 2013-11-07 14:29:49 UTC ---
no, the optional "Default-Enabled" key in the header of the init script would
override any "-y" on the macro invocation.
SV_VALUE=`sed -n -e "/$SV_B/,/$SV_E/{/^#
[^[:space:]]*$SV_KW:[[:space:]]*\([^[:space:]]*\).*/s//\1/p;}" <
/etc/init.d/$SCRIPTNAME`
test "$FORCE_YES" = "1" && SV_VALUE="yes"
test -n "$SV_VALUE" || SV_VALUE="yes"
so we end up with "SV_VALUE" set to "yes" (but as we have not specified "-Y"
as option we have FORCE_YES=0)
FIRST_ARG is simply $1 when calling the postinstall script, which is 1 for
initial installation of a package and 2 for update of a package.
a few lines further:
if test "$FIRST_ARG" = "1" -a "$SV_VALUE" = "no" ; then
/sbin/insserv ${YAST_IS_RUNNING:+-f} -r /etc/init.d/$SCRIPTNAME
elif test "$FIRST_ARG" = "1" -o "$FORCE_YES" = "1" ; then
/sbin/insserv ${YAST_IS_RUNNING:+-f} /etc/init.d/$SCRIPTNAME
fi
so if FIRST_ARG is not 1, then only FORCE_YES will lead to calling insserv
to activate the script.
So this usually breaks only for renamed packages, where rpm has no way of
telling a new install from an update, but for all normal cases, this use of
the macro will not re-enable anything during a package update.
--
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.