W/o /etc/init.d/ipsec the package is cannot be used.

The missing file is based on:

libreswan/initsystems/sysvinit/ipsec.init.in

[A wrong version of this email might have gone out; please ignore it in
favour of this version. -JimC]

The missing file is based on:

libreswan/initsystems/sysvinit/init.debian.in

Hi there!
 […]

Thanks for the report.  I don't have any systems remaining that run
sysvinit that i would be able to use to test libreswan, so i'm
uncomfortable shipping any such automated system integration.  I'd be
similarly uncomfortable maintaining a package that proposed libreswan
system integration for other initsystems using runit-init or openrc.

So for now the debian package for libreswan only provides integration
with the systemd initsystem.

If anyone wants to propose specific patches to the debian packaging to
either have the main libreswan package automatically support sysvinit
(or any other initsystem) or produce a libreswan-sysvinit (or
libreswan-runit, etc) binary package, and that the patch author
volunteers to help test and maintain that system integration work over
time, i'd be open to reviewing and incorporating reasonable changes into
the debian packaging.

It's not something i'm likely to work on myself, though.

Regards,

On Mon, 20 Feb 2017 23:26:34 -0500 Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:

Hi Daniel,

I tested libreswan init script, and it works just fine. If you need
any proofs/logs -- I can provide them.

Frankly, I don't see any reason to not include sysvinit script to the
package, as it's supported in upstream. Granted, you can't test it,
but you probably isn't testing 100% of libreswan functional either
(correct me if I'm wrong). Still you do provide the package for it. So
this logic just doesn't work here, sorry :) I can be a little harsh,
but I was really disappointed when I couldn't make Debian package
work, just because I'm using sysvinit, and even more disappointed,
when I found that sysvinit script actually exists in upstream
libreswan code...

Debian supposed to be modular OS (at least that's how I understand
"Universal operating system" motto on the home page), so that it's
easy to change any component (e.g. display manager, terminal, init
system). Of course, some packages really tightly depend on systemd.
But this is not the case here, right?

If you really need any help with sysvinit script testing/packaging --
please do mention specific (reasonable) steps you need from my side,
and I will gladly provide it. As for suggested above
"libreswan-sysvinit" package: I'd really like to have single package
for both systems. Because:
 1. It's doable
 2. A lot of people continue using sysvinit in Debian
 3. It would be ugly to support two different packages for the same component

Thanks.

Great, i'm glad to hear it.  Do you have a patch to provide for the
debian packaging?  I've already offered to review such a patch (in the
text that you quoted above).

All the best,

Control: tags 855653 + moreinfo

Just following up on #855653 because I haven't seen anyone offer a
tested, considered patch for the debian libreswan packaging to handle
sysvinit.  Looking in the upstream source tree, i see:

    initsystems/sysvinit/init.debian.in

but it has a fair amount of fiddliness in it, and it is clearly out of
date (even in version 4.2, it references KLIPS!) so i suspect this is
not something anyone is actually maintaining.

Again, I'm happy to review proposed patches from someone who has tested
them on a system running sysvinit.