Ian Jackson writes ("Bug#1039361: SAUCE systemd unit"):
> OK, I guess I will have a go at this myself this weekend.

I converted the package to use dh_installinit and dh_installdeb.
That's in 0.9.5 which I just uploaded.

I wrote a service file based on the systemd documentation I could
find, which calls the existing init script.  (I think this is probably
the best approach, but I'm not sure.)

But it does not work.  My autopkgtests fail.  I'm running

  git-clean -xdff && dpkg-buildpackage -uc -b && autopkgtest 
../sauce_0.9.5~~_all.deb . --- /usr/sbin/really autopkgtest-virt-qemu 
/volatile/ian/autopkgtest-virt-qemu/forky

where that image came from really autopkgtest-build-qemu forky forky.

It's evidently running my unit file, since that's the change to
the .deb and without it everything works, presumably via systemd's
init script compatibility report, whose planned removal is what this
bug is about.

I'm not sure how to debug this.  I'm not a habitual user of qemu, so
I' m not sure even how to log into the qemu VM, and if I did I
wouldn't know how to debug a system service startup.

My branch is at
   git clone git+ssh://login.chiark.greenend.org.uk/home/ian/things/Sauce/sauce 
-b systemd-draft

My feeling is that converting this package to use the dh sequencer, or
generally overhauling the rules file, isn't a particularly useful
thing to be doing.  But I could be wrong, especially if that's likely
to be implicated in the problems I'm having with systemd.

Ian.

-- 
Ian Jackson <[email protected]>   These opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Reply via email to