Hi Steve, thanks for reporting this, and for the hint on how to fix it. We currently have a shell script in our prerm script, which manually stops all our systemd units:
https://github.com/snapcore/snapd/blob/master/packaging/ubuntu-16.04/snapd.prerm Do I correctly understand that your suggestion is not to do that? I'm actually a bit confused (though this is probably a question for my own team) why we have that prerm script, when we are already using dh_systemd_start in out debian/rules file: ============== override_dh_systemd_start: # Due to https://github.com/systemd/systemd/issues/8102 # debhelper supporting --remaining like behaviour here would # have been useful # (Re-)start socket first dh_systemd_start snapd.socket # Then service dh_systemd_start snapd.service # Then the rest dh_systemd_start $(filter-out snapd.socket snapd.service, $(shell ls debian/snapd/lib/systemd/system/)) ============== wouldn't this rule already cause the units to be stopped at the prerm step (we are using debhelper compatibility level 9)? Anyway, I'm soon going to propose a PR, so we can discuss over it. ** Bug watch added: github.com/systemd/systemd/issues #8102 https://github.com/systemd/systemd/issues/8102 ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
