Upload of -3, stabilizing (was Re: Debug package)

[Fabian Fagerholm]

On Tue, 2006-11-14 at 17:58 +0200, Fabian Fagerholm wrote:
> My current thinking is that we go through NEW with -dbg starting in two
> days or so,

I just uploaded -3. I gave it an extra day in the hope that we might be
able to solve some of the Postfix integration issues, but right now the
NEW processing takes precedence. We can fix the Postfix issues in -4.

> then we look at our status and try iron out any remaining
> issues, aiming for stability.

Right now, I'd say the priority issues are:

Postfix integration (for example, #398534, #388562). This is a
regression from sarge, but it should be easy to fix once the problem is
pinpointed. To investigate, install Postfix and configure it with
different kinds of SASL authentication, making note of the steps
required. Another good way is to pick a suitable tutorial and follow it,
making note of things that don't work (and judging whether it's a fault
in the tutorial or in our package).

Suspected memory leaks (for example, #153915, #379810). Some of causes
are known, others need investigation with valgrind or similar tool.

Segfaults (for example, #365756, #365744, #220837). These could be
possible to fix once the -dbg package is available.

However, I only consider the Postfix integration to be a prerequisite
for etch -- memory leaks and segfaults have plagued this library for a
long time, and thus would not be a regression compared to the sarge
version.

So everybody: install Postfix+SASL! :)

Cheers,
-- 
Fabian Fagerholm <fabbe at paniq.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20061117/7788441d/attachment.pgp