Burn this fucking madness .. there is no reason to mess with yunohost-firewall during postinst, and it doesnt even actually restart it because $2 is always empty, so what the actual fuck.

This commit is contained in:
Alexandre Aubin 2019-11-22 19:05:14 +01:00
parent 625df81872
commit 978d9d5dfd

24
debian/postinst vendored
View file

@ -16,12 +16,6 @@ do_configure() {
echo "Launching migrations.."
yunohost tools migrations migrate --auto
# restart yunohost-firewall if it's running
service yunohost-firewall status >/dev/null \
&& restart_yunohost_firewall \
|| echo "yunohost-firewall service is not running, you should " \
"consider to start it by doing 'service yunohost-firewall start'."
fi
# Change dpkg vendor
@ -39,24 +33,6 @@ do_configure() {
pam-auth-update --package
}
restart_yunohost_firewall() {
echo "Restarting YunoHost firewall..."
deb-systemd-helper unmask yunohost-firewall.service >/dev/null || true
if deb-systemd-helper --quiet was-enabled yunohost-firewall.service; then
deb-systemd-helper enable yunohost-firewall.service >/dev/null || true
else
deb-systemd-helper update-state yunohost-firewall.service >/dev/null || true
fi
if [ -x /etc/init.d/yunohost-firewall ]; then
update-rc.d yunohost-firewall enable >/dev/null
if [ -n "$2" ]; then
invoke-rc.d yunohost-firewall restart >/dev/null || exit $?
fi
fi
}
# summary of how this script can be called:
# * <postinst> `configure' <most-recently-configured-version>
# * <old-postinst> `abort-upgrade' <new version>