Dear Maintainer, snapper seems not to ship the neccessary scripts to run on systems with sysv init. It installs .timer units for systemd, but probably requires cron.d scripts on systems with sysvinit, which seem to be missing. (The attached system information is from a system that booted with systemd and has a working snapper, but still does not have sysv scripts installed. The problem occurs on a debian buster system with sysvinit-core installed) with kind regards, Alex
It looks like the regression may be introduced with the fix for Bug #791726, in which it looks like you just removed the cron scripts without adding another fallback for non-systemd systems.
Dear Maintainer, Here is my patchset which re-enables and improves the cron scripts for snapper, restoring scheduled snapshotting functionality on systems which don't support systemd timers on account of using non-systemd init systems. This patchset can be applied to the debian packaging repository at https://salsa.debian.org/debian/snapper.git using the git-am(1) command. This patchset is composed of a few different parts. The first part, patches 0001, 0002, and 0003, merely bring the packaging repository up-to-date with respect to the two most recent NMUs. Patches 0001 & 0002 bring the debian/sid branch up to debian/0.10.6-1.1 and patch 0003 up to debian/0.10.6-1.2. The second part, patches 1004 and 1005, revert two previous commits that removed the cron scripts from the generated binary packages. This removal was originally done as a quick fix for #791726. The third part, patches 1006 and 1007, make two enhancements to the cron scripts. 1006 adds a check early in the scripts that will cause them to abort if the snapper binary is not found. This fixes the original issue that prompted the filing of #791726. 1007 adds a similar early check to the scripts that causes them to abort if systemd is detected. This prevents the cron scripts running in addition to the systemd timers on systemd-using systems. Finally, the last part, patch 1008, updates the debian/changelog file. Please let me know if you have any questions or if you would like me to make any modifications and submit a v2 changeset. Thanks,
Dear Maintainer, Here is a minor revision of and replacement to the patchset I submitted yesterday. After submitting the original patchset I noticed a slight discrepancy with the git commits I had made to record the changes made to the packaging by the last few NMUs. I had based my commits on the patches submitted to the BTS for the #1062906 and #1073699 bugreports and at least in the case of #1062906 there was a minor difference between those patches and what was actually uploaded to the archive. I have now corrected this. As before, this corrected patchset can be applied to the debian packaging repository at https://salsa.debian.org/debian/snapper.git using the git-am(1) command. For completeness, a corrected patchset summary follows. This patchset is composed of a few different parts. The first part, patches v2-0001, v2-0002, and v2-0003, merely brings the packaging repository's debian/sid branch up-to-date from its current position at the debian/0.10.6-1 tag to the latest package version in the Debian package archive. Patch v2-0001 brings the branch up to version 0.10.6-1.1~exp1, patch v2-0002 up to version 0.10.6-1.1, and patch v2-0003 up to version 0.10.6-1.2. The second part, patches v2-1004 and v2-1005, revert two previous commits that removed the cron scripts from the generated binary packages. This removal was originally done as a quick fix for #791726. The third part, patches v2-1006 and v2-1007, make two enhancements to the cron scripts. v2-1006 adds a check early in the scripts that will cause them to abort if the snapper binary is not found. This fixes the original issue that prompted the filing of #791726. v2-1007 adds a similar early check to the scripts that causes them to abort if systemd is detected. This prevents the cron scripts running in addition to the systemd timers on systemd-using systems. Finally, the last part, patch v2-1008, updates the debian/changelog file. Again, please let me know if you have any questions or if you would like me to make any further modifications and submit a v3 changeset. Thanks,