On Mon, 20 Feb 2017 23:26:34 -0500 Daniel Kahn Gillmor <[email protected]> wrote: > Control: severity 855653 wishlist > Control: retitle 855653 please provide libreswan sysvinit integration > > Hi there! > > On Mon 2017-02-20 18:08:02 -0500, [email protected] wrote: > > W/o /etc/init.d/ipsec the package is cannot be used. > > > -- System Information: > > Debian Release: 9.0 > > APT prefers unstable > […] > > Init: sysvinit (via /sbin/init) > > 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. >
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. > It's not something i'm likely to work on myself, though. > > Regards, > > --dkg > >
