Package: apticron Version: 1.1.56 Severity: wishlist Dear Maintainer,
as a fix for bug 752506, bcron-run chose to provide cron-daemon rather than cron, which looks correct to me. Except that the new bcron-run and apticron don't work well together: apt-get upgrade leaves me with the old version, apt-get upgrade suggests replacing it with cron (which I don't want). I realize that depending on cron-daemon isn't a perfect solution since at apticron depends on /etc/cron.d, which isn't honored by at least one of the packages that provide cron-daemon (systemd-cron). It's not clear to me is systemd-cron can/will support cron.d, but it seems like it won't; according to bug 752376, there's a project to fix that, basically by parsing cron entries and write them in a format that systemd understands. It seems like apticron used cron.daily in the past, but then switched away due to bug 587597; since the only problem was clarity, imho it could just run both scripts with the --cron option, adding a comment inside them along the lines of "# yes, there are two scripts; it's to accomodate different setups.", and that would allow depending on cron-daemon even for people running the broken systemd-cron. Any problem with that? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apticron depends on: ii apt 1.0.6 ii bcron-run [cron] 0.09-13 ii bsd-mailx [mailx] 8.1.2-0.20131005cvs-1 ii bzip2 1.0.6-7 ii debconf [debconf-2.0] 1.5.53 ii dpkg 1.17.11 ii ucf 3.0030 Versions of packages apticron recommends: ii apt-listchanges 2.85.13 ii iproute2 3.16.0-1 apticron suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
