dh-systemd: dh_systemd_start --no-start --restart-after-upgrade causes the service to be started on install

[Michael Biebl]

Am 13.10.2016 um 18:08 schrieb Michael Biebl:
> Am 13.10.2016 um 17:56 schrieb Michael Biebl:
>> Am 13.10.2016 um 17:47 schrieb Felipe Sateler:
>>> On 13 October 2016 at 12:36, Michael Biebl <biebl at debian.org> wrote:
>>>>
>>>> With compat level 9 and older, --no-start did not generate any
>>>> maintainer scripts code at all.
>>>
>>> You can get the same with dh 10 with --no-start --no-restart-after-upgrade

> fwiw, in network-manager I use
> 
>> override_dh_systemd_start:
>>        dh_link lib/systemd/system/NetworkManager.service \
>>                lib/systemd/system/network-manager.service
>>        dh_systemd_start -pnetwork-manager --no-start NetworkManager-dispatcher.service
>>        dh_systemd_start -pnetwork-manager --no-start NetworkManager-wait-online.service
>>        dh_systemd_start -pnetwork-manager --restart-after-upgrade NetworkManager.service


For some reason --no-start --no-restart-on-upgrade still generates code
for NetworkManager-dispatcher.service.

Something odd going on here. Maybe dh_systemd_start get's confused by the
[Install]
Also=NetworkManager-dispatcher.service

in NetworkManager.service

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20161013/958acb27/attachment.sig>