[Pkg-mailman-hackers] Bug#615204: add cull_bad_shunt to mailman cronjob

[Thijs Kinkhorst]

Package: mailman
Severity: wishlist

Hi Timo,

On Monday 21 February 2011 13:09:39 Timo Veith wrote:
> Hello debian mailman hackers,
> 
> I'v got a question according to the mailman package of Debian lenny. Today
> a security update came in and I had some very old psv files left in
> /var/lib/mailman/qfiles/bad which prevented the upgrade to succeed. By
> googling I found out that I can/should use the cron job
> /var/lib/mailman/cron/cull_bad_shunt to remove them. This brought me to the
> conclusion that I should set up a cron job for the list user. But normally
> this should be mentioned somewhere in the setup instructions so I searched
> there. All I#ve found were some hints that one must activate the news gate
> cron job if needed. And that formerly the qrunner was started by a cron
> job. But this is done with the init script nowadays. Also there is a
> crontab.infile under /usr/lib/mailman/cron in which the cron job from
> above is
> mentioned among others. In the comment of one of the others a
> GZIP_ARCHIVE_TXT_FILES variable is referenced. I couldn't find that in
> mm_cfg.py.
> 
> So now the question arises do I need to setup cron jobs for mailman as the
> list user or is this taken care of by the mailmanctl somehow?
> 
> Please direct me to the docs, if this is written down somewhere!

Thanks. This is indeed an incompleteness of the current cronjob. Unfortunately 
the way the cronjob is currently managed in the Debian packaging is quite 
convoluted, I will see if I can get it added in some way.


Thijs