sanlock 3.6.0-1 breaks on install missing sanlock user

[Christian Ehrhardt ]

Since 3.6.0-1 (recently synced and now in proposed) installation fails.

# apt install sanlock
[...]
Setting up sanlock (3.6.0-1) ...
addgroup: The user `sanlock' does not exist.
dpkg: error processing package sanlock (--configure):

Since by that it became uninstallable it also breaks all builds which depend on libsanlock-dev.

[Christian Ehrhardt  (paelzer)]

Issue is trivial, fix tested by repackaging:

  apt-get download sanlock
  dpkg-deb -x sanlock_3.6.0-1_amd64.deb sanlock
  dpkg-deb -e sanlock_3.6.0-1_amd64.deb sanlock/DEBIAN
  vim sanlock/DEBIAN/postinst
Change order of user creation and adding to the group.

  dpkg-deb -b sanlock sanlock_3.6.0-1ubuntu1~ppa1_amd64.deb
  dpkg -i sanlock_3.6.0-1ubuntu1~ppa1_amd64.deb

Now working

[Christian Ehrhardt  (paelzer)]

Built the normal way and fixed another bug that was reported in Debian still working fine atm:
Unpacking sanlock (3.6.0-1ubuntu1) over (3.6.0-1) ...
Setting up sanlock (3.6.0-1ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (235-3ubuntu3) ...
Processing triggers for man-db (2.7.6.1-4) ...

Proposing a MP before uploading ...

[Launchpad Janitor (janitor)]

This bug was fixed in the package sanlock - 3.6.0-1ubuntu1

---------------
sanlock (3.6.0-1ubuntu1) bionic; urgency=medium

  * d/sanlock.postinst: run addgroup after creating the user (LP: #1745922)
  * d/rules: install systemd-wdmd (Closes: #854696)

 -- Christian Ehrhardt <email address hidden> Mon, 29 Jan 2018 07:19:29 +0100

[Christian Ehrhardt  (paelzer)]

All fixes in Debian now, triggered a sync to make it an autosync again.