Bug#344996: Cron job continues even after debsecan is removed

2006-02-08 Thread Florian Weimer
* Greg Kochanski: >> Technically, the cronjob is treated as a configuration file, and >> it's only removed during purge. > That sounds like a bad thing, and I've run across that before. > Is that Debian policy? Sort of. The treatment of configuration files is the reason why there is both dpkg -

Bug#344996: Cron job continues even after debsecan is removed

2006-02-06 Thread Florian Weimer
* Greg Kochanski: > I see this: > > Feb 6 21:32:01 gpk /USR/SBIN/CRON[21289]: (daemon) CMD (test -x > /usr/bin/debsecan && /usr/bin/debsecan --mailto root --cron) But I hope you don't receive any funny email messages. > after this: > > $ sudo apt-get remove debsecan > Reading package lists...

Bug#344996: Cron job continues even after debsecan is removed

2006-02-06 Thread Greg Kochanski
Package: debsecan Version: 0.3.4 Followup-For: Bug #344996 I see this: Feb 6 21:32:01 gpk /USR/SBIN/CRON[21289]: (daemon) CMD (test -x /usr/bin/debsecan && /usr/bin/debsecan --mailto root --cron) after this: $ sudo apt-get remove debsecan Reading package lists... Done Building dependency tr