Hi, yes you are correct, it currently doesn't set it to enable any more. Sorry about that.
Looks like it was enabled when I initially installed in on 8 March 2017. It just kept the enabled status in later upgrades. Thanks. lrwxrwxrwx 1 root root 16 Mar 8 2017 K01gdomap -> ../init.d/gdomap lrwxrwxrwx 1 root root 16 Mar 8 2017 K01gdomap -> ../init.d/gdomap lrwxrwxrwx 1 root root 16 Mar 8 2017 S03gdomap -> ../init.d/gdomap lrwxrwxrwx 1 root root 16 Mar 8 2017 S03gdomap -> ../init.d/gdomap lrwxrwxrwx 1 root root 16 Mar 8 2017 S03gdomap -> ../init.d/gdomap lrwxrwxrwx 1 root root 16 Mar 8 2017 S03gdomap -> ../init.d/gdomap lrwxrwxrwx 1 root root 16 Mar 8 2017 K01gdomap -> ../init.d/gdomap On Sat, 2018-11-17 at 00:16 +0200, Yavor Doganov wrote: > Control: tags -1 = moreinfo unreproducible > > jfp wrote: > > Package: gnustep-base-runtime > > Version: 1.25.1-4+b1 > > On install of gnustep-base-runtime (dependency of unar) > > > > It set the gdomap service to autotart. > > Thanks for the report but I'm afraid I can't reproduce this: > > $ systemctl status gdomap > ● gdomap.service - LSB: Start the GNUstep distributed object mapper > Loaded: loaded (/etc/init.d/gdomap; generated) > Active: inactive (dead) > Docs: man:systemd-sysv-generator(8) > > $ systemctl is-enabled gdomap > gdomap.service is not a native service, redirecting to systemd-sysv- > install. > Executing: /lib/systemd/systemd-sysv-install is-enabled gdomap > disabled > > That should be the case for new installations AFAICT. > > > Fix is: > > in /etc/init.d/gdomap > > change > > # Default-Start: 2 3 4 5 > > to > > # Default-Start: > > Are you sure? I don't think this LSB header is relevant for systemd > but I'm not familiar enough with it to be certain. > > Anyway, I'll also pass --no-start to dh_installinit, fortunately it > helps...
