Your message dated Sat, 08 Oct 2011 15:49:30 +0000
with message-id <[email protected]>
and subject line Bug#615204: fixed in mailman 1:2.1.14-3
has caused the Debian Bug report #615204,
regarding add cull_bad_shunt to mailman cronjob
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
615204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615204
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: mailman
Source-Version: 1:2.1.14-3
We believe that the bug you reported is fixed in the latest version of
mailman, which is due to be installed in the Debian FTP archive:
mailman_2.1.14-3.debian.tar.gz
to main/m/mailman/mailman_2.1.14-3.debian.tar.gz
mailman_2.1.14-3.dsc
to main/m/mailman/mailman_2.1.14-3.dsc
mailman_2.1.14-3_amd64.deb
to main/m/mailman/mailman_2.1.14-3_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thijs Kinkhorst <[email protected]> (supplier of updated mailman package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 08 Oct 2011 17:27:51 +0200
Source: mailman
Binary: mailman
Architecture: source amd64
Version: 1:2.1.14-3
Distribution: unstable
Urgency: low
Maintainer: Mailman for Debian <[email protected]>
Changed-By: Thijs Kinkhorst <[email protected]>
Description:
mailman - Powerful, web-based mailing list manager
Closes: 597112 615204
Changes:
mailman (1:2.1.14-3) unstable; urgency=low
.
* Make man page descruptions match more keywords (closes: #597112).
* Add cull_bad_shunt command to default cron job (closes: #615204)
and improve cron job handling in the package.
* Import dpkg buildflags, also enabling hardening features.
* Remove gate_news debconf question.
Checksums-Sha1:
0dc3ab75b3d681e967c142d72f8e3da34d9504ff 1689 mailman_2.1.14-3.dsc
755b171f76b76f9211c1adb91f5c91792dcc7b8e 102268 mailman_2.1.14-3.debian.tar.gz
cd5d83948db18f432520871bc580c6a3f351a915 9717308 mailman_2.1.14-3_amd64.deb
Checksums-Sha256:
cf3a0a91e5e7e0cc935ff8dfd9436df194b4f54756b87d42400a5fc1327b2be5 1689
mailman_2.1.14-3.dsc
c1d96ee099c215a435ec85a6ed1facb83265e0280dced1f809f0645a66e480af 102268
mailman_2.1.14-3.debian.tar.gz
445ee57d0235ff56fd87a7d96e34b9297f4951b2205cc8b40b1f69295593291d 9717308
mailman_2.1.14-3_amd64.deb
Files:
7673269c58365e2c125cd3bb93f76020 1689 mail optional mailman_2.1.14-3.dsc
c77d720c326aef28ec87f9ee6eb76585 102268 mail optional
mailman_2.1.14-3.debian.tar.gz
89d5ad111981cc639ace801462bde056 9717308 mail optional
mailman_2.1.14-3_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJOkG9lAAoJEOxfUAG2iX57anMH/1jDVAhRn1GGoq++Gi+oByDP
KgiemW6YpTfqK6kqGDy0XfpcDpL5+hBb4xlsTB4w/HY2GQHM/UCkBozdfVQ2DRkz
8j0hpIBK9DlA8kropQEk/hYMAV9ZdO7nhQbJ1STG+2Os9YiO9f2SC592p8q8Fb/a
/nlwK/beQZTROB9cdctPMwwyTYy9DXgVsVkCgCXvYdTG9Nm9HxSSPBUoVuLhpYOj
AtI/I0uKH6xreztIMqs8zhPAxeaI7Nf/Yz2vQ4ullr2U3BRREQPWVYBqOyY4UCUw
MzosxuvUibor+HnM0/fmon4Zc9b/plUc5zHNaXmoztROYGeUGam4gIlEORfdwgk=
=dEcj
-----END PGP SIGNATURE-----
--- End Message ---
