Accepted teapop 0.3.5-1 (i386 source)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 18 Dec 2002 20:00:37 +1300
Source: teapop
Binary: teapop teapop-pgsql teapop-mysql
Architecture: source i386
Version: 0.3.5-1
Distribution: unstable
Urgency: high
Maintainer: Nick Phillips <nwp@lemon-computing.com>
Changed-By: Nick Phillips <nwp@lemon-computing.com>
Description:
teapop - Powerful and flexible RFC-compliant POP3 server
teapop-mysql - Powerful and flexible RFC-compliant POP3 server
teapop-pgsql - Powerful and flexible RFC-compliant POP3 server
Closes: 148995 172312 172756
Changes:
teapop (0.3.5-1) unstable; urgency=high
.
* Add section to debian/rules to deal with DEB_{HOST,BUILD}_GNU_TYPE
as per autotools-dev 20020320.1 docs.
* Rename configure.in to configure.ac to get it processed by autoconf
2.5x (less likely to lead to errors than trying to remember to
insert AC_PREREQ each time upstream configure.in changes).
* correct building of SELECT string in pop_mysql.c to build query
correctly when pmailrow is not specified, and tidy up equivalent part
of pop_pgsql too (change now incorporated upstream) - Closes: #148995
* IMPORTANT: New upstream version improves signal handling during POP
DELE operations; this may fix some data loss issues - Closes: #172756
* Removed CVS cruft - Closes: #172312
* Incorporated fix to handling of null bytes in mboxes from development
version, and carried it over to maildir handling.
IMPORTANT: Whilst this fixes a potential data loss issue with mboxes,
the issue with maildirs was never as serious, and the updated maildir
code is currently (2002/12/17) barely tested (although the change is
minor).
There is also still a potential issue, although I don't believe it is
serious, if the last line of an mbox or maildir mail file is an
exact multiple of 1023 chars long... although it appears that with
both mboxes and maildirs, last lines are _supposed_ to be empty.
Upstream is disinclined to fix this issue due to the overhead
imposed in the normal case.
* Replaced non-free RSA MD5 implementation with Colin Plumb's Public
Domain version. For some reason I was under the impression that we
were building with a system MD5 library rather than the non-free code
in the upstream teapop package. Apologies.
* Don't install cronpopauth.pl or create ${localstatedir} as we're not
building a binary with which they will be useful anyway (look for
cronpopauth in "Makefile.in" files to see how to revert this).
A better solution here would be nice.
* Apologies also to Clint; _still_ no LDAP version. Coming soon,
promise...
Files:
da10ebef9e0d2ac818859bdb43d435fe 631 mail extra teapop_0.3.5-1.dsc
65fdea12d76c1ed45d65689f48f7f994 139858 mail extra teapop_0.3.5.orig.tar.gz
8be2e0dd7f70ee5d0057975093edda4c 113332 mail extra teapop_0.3.5-1.diff.gz
18ae0d04228914929b0e8c9a4f6a2f78 56382 mail extra teapop_0.3.5-1_i386.deb
db8ccfc9c382aa3af5f5a875f5b0a5f0 58108 mail extra teapop-mysql_0.3.5-1_i386.deb
b38554a5ad2a8162d78789b13616f4c8 57704 mail extra teapop-pgsql_0.3.5-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+AGWHdZJIm8yYOSgRAkgSAJ9inaHkmfsXMRZ2il6yc/EENAVBfQCg3TBS
Lpyok5Kj5K/2ddjzq3yffXA=
=J6pG
-----END PGP SIGNATURE-----
Accepted:
teapop-mysql_0.3.5-1_i386.deb
to pool/main/t/teapop/teapop-mysql_0.3.5-1_i386.deb
teapop-pgsql_0.3.5-1_i386.deb
to pool/main/t/teapop/teapop-pgsql_0.3.5-1_i386.deb
teapop_0.3.5-1.diff.gz
to pool/main/t/teapop/teapop_0.3.5-1.diff.gz
teapop_0.3.5-1.dsc
to pool/main/t/teapop/teapop_0.3.5-1.dsc
teapop_0.3.5-1_i386.deb
to pool/main/t/teapop/teapop_0.3.5-1_i386.deb
teapop_0.3.5.orig.tar.gz
to pool/main/t/teapop/teapop_0.3.5.orig.tar.gz
Reply to: