[opensuse-packaging] What does rpm macro %insserv_cleanup do
Summary: the rpm macro %insserv_cleanup expands to 'sbin/insserv etc/init.d' what looks not good. Is this correct or not? More details: When packaging kolab without the macro %insserv_cleanup, I get the following warning: RPMLINT report: =============== kolab.noarch: W: postun-without-%insserv_cleanup /etc/init.d/kolab kolab.noarch: W: postun-without-%insserv_cleanup /etc/init.d/kolabd The package doesn't have a %insserv_cleanup call in %postun Following the suse convention I add the macro, according: http://en.opensuse.org/SUSE_Package_Conventions/Init_Scripts in spec file %postun .... %insserv_cleanup In rpm postun section: rpm -qp --scripts /var/tmp/build-root-openSUSE_11.1- i586/usr/src/packages/RPMS/noarch/kolab-2.2.2.90_cvs20091214-0.noarch.rpm ........ postuninstall scriptlet (using /bin/sh): ...... sbin/insserv etc/init.d <<<<<< strange line What is that line doing. When executing it, it results in: -bash: sbin/insserv: No such file or directory The macro is defined as: In /usr/lib/rpm/suse.macros: # macro: insserv_cleanup %insserv_cleanup() \ sbin/insserv etc/init.d When adding it as, e.g.: %insserv_cleanup kolabd or %{insserv_cleanup kolabd} -- Richard -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 14/12/09 17:59, Richard Bos wrote:
Summary: the rpm macro %insserv_cleanup expands to 'sbin/insserv etc/init.d' what looks not good. Is this correct or not?
Yes, it is correct.
%insserv_cleanup ^^
That's the correct way. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Christian, Op maandag 14 december 2009 22:17:46 schreef Cristian Rodríguez:
On 14/12/09 17:59, Richard Bos wrote:
Summary: the rpm macro %insserv_cleanup expands to 'sbin/insserv etc/init.d' what looks not good. Is this correct or not?
Yes, it is correct.
%insserv_cleanup
^^
That's the correct way.
But what is it doing, I don't understand. As the macro expands to this: 'sbin/insserv etc/init.d' It's not a line that can be executed, but it is part of the postuninstall script. As such it will be executed. Looks to me that it will result in an error.... -- Richard -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 14/12/09 18:29, Richard Bos wrote:
But what is it doing, I don't understand.
from TFM ;) "In this case insserv does not add or remove a script to the run- levels declared in the script headers, but may re-order the runlevels if the order of the currently enabled scripts has changed" As the macro expands to this:
'sbin/insserv etc/init.d' It's not a line that can be executed, but it is part of the postuninstall script. As such it will be executed. Looks to me that it will result in an error....
It is called from the root directory... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Cristian, Op maandag 14 december 2009 22:58:54 schreef Cristian Rodríguez:
from TFM ;)
"In this case insserv does not add or remove a script to the run- levels declared in the script headers, but may re-order the runlevels if the order of the currently enabled scripts has changed"
As the macro expands to this:
'sbin/insserv etc/init.d' It's not a line that can be executed, but it is part of the postuninstall script. As such it will be executed. Looks to me that it will result in an error....
It is called from the root directory...
Thanks a lot Cristian, it is clear now! -- Richard -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (2)
-
Cristian Rodríguez -
Richard Bos