[Amavisd-new-debian-devel] Amavisd-new 2.3.3-1 in experimental
Henrique de Moraes Holschuh
hmh at debian.org
Sat Oct 22 17:20:05 UTC 2005
I have just done a full cleanup and upload to experimental.
The things that are still missing for an upload to unstable IMHO are:
1. UCF support for conf.d/*
2. Move all but *really don't muck with this* debian defaults to /etc
3. Move all the AV definitions into their own file if in /etc, for
easier user handling
4. Go over the BTS and Mark's notes, and populate the changelog with
proper (closes: #) entries. Instead of doing it all on the newest
entry, do on the proper entires.
5. Think over some of the Debian defaults and config tweaks, a list
of the stuff missing/needing some work that I found is in debian/TODO
Finally, when the above is done, upload a build that uses dpkg-buildpackage
-v20030616p10-5 to unstable. Whatever we do, we must not forget that -v.
I am running amavisd-new 2.3.3-1 in production, now. It is ready for an
unstable upload, as far as stability and the code are concerned.
The only lasting doubt is the perl utf8+taint crap. Anyone recalls the test
we had devised to cause amavisd-new to lockup if perl was still b0rked? I
want to revisit safe_encode and safe_decode, and if at all possible revert
to what is upstream.
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
More information about the Amavisd-new-debian-devel