distro: packaging updates
@dkg Hi.
I'm removing some obsolete package dependencies from debian package in this MR.
Some of our users also noticed the debian packages don't trigger a service restart when the package is updated. Is this intentional due to some debian policy or a bug? I think it'd make more sense to restart the service - what would be the proper place to trigger this?
Merge request reports
Activity
the debian changes all look fine to me, and have been merged into 2.3.0-1 in debian already.
as for restarting the services upon upgrade, i agree that it's a potential problem. I'm not convinced that "restart" is the right thing to do (for socket-activated services, they might not already be running), but maybe "stop" is the right thing?
@dkg Perhaps the cleanest solution would be to:
systemctl try-restart system-kresd.slicewhich should ensure a restart for all running kresd instances, but wouldn't start them in case they aren't running already.
I'm just not sure where is the proper place to execute this command in the debian packaging files.
added 65 commits
- 2e1d845d...7fae33f4 - 57 commits from branch
master - 9a127a24 - distro/deb: reformat knot-resolver.dsc
- 27c2c7f3 - distro/arch: reformat dependencies
- 66b95f23 - distro/rpm: reformat spec file
- 7afad04e - distro/*: remove obsolete memcached and redis dependency
- a54d885e - distro/rpm: use Python3 to build doc
- 80e323cb - distro/deb: remove obsolete dependencies libjansson and python3
- 3a17104e - distro/arch: add missing dependencies
- fb3c87c1 - distro/rpm/knot-resolver.spec
Toggle commit list- 2e1d845d...7fae33f4 - 57 commits from branch
added 2 commits
- 5e043b3b - distro/rpm: handle systemd restarts in CentOS 7 compatible way
- 5dd67f89 - systemd: man page - update about system-kresd.slice
added 1 commit
- b9c6b876 - systemd: man page - update about system-kresd.slice
-
Debian service restart solved in !589 (closed) (!593 (merged)).
enabled an automatic merge when the pipeline for b9c6b876 succeeds
mentioned in commit c4e904e1