[Pkg-systemd-maintainers] Bug#717603: Acknowledgement (How to handle service files, where [Install] has changed)

[Michael Stapelberg]

Hi,

Michael Stapelberg <stapelberg at debian.org> writes:
> 1) Install p1 1.0-1, verify the state file gets created and contains the
>    service file. Verify the service file is enabled.
> 2) Upgrade to p1 1.0-2, verify the state file gets updated and the alias
>    gets created.
> 3) Purge p1, verify the state file gets deleted and the service file and
>    alias symlinks get deleted.
>
> 4) Repeat 1, 2, 3, but disable the service after 1 and ensure it does
>    not get re-enabled after 2.
This works flawlessly.

> 5) Install p2 1.0-1, verify the state file gets created but the service
>    file is not enabled.
> 6) Upgrade to p2 1.0-2, verify the state file gets updated, the service
>    is still not enabled and the alias was created.
The alias does not get created. This is because we don’t run
“deb-systemd-helper enable” in this situation. I think we should, and
run “deb-systemd-helper disable” on first installation, which should
create the state files so that the enable is a noop.

> 8) Repeat 5, 6, 7, but enable the service after 5 and ensure it stays
>    enabled after 6 and gets disabled after 7.
This works flawlessly.

> 9) Install p3 1.0-1, verify the state file gets created and both service
>    files are in the state file and enabled.
> 10) Upgrade to p3 1.0-2, verify the state file does not contain the
>     dropped file anymore and the dropped file’s symlink is deleted.
>
> 11) Repeat 9, 10, but disable the to-be-dropped service file after 9 and
>     verify it still gets removed from the state file.
This works flawlessly.

-- 
Best regards,
Michael