On Sat, 2006-06-10 at 11:50 +0200, Mohammed Adnène Trojette wrote: > Hi Roberto, hi, Debian Cyrus SASL2 Team! Hi Mohammed! (I'm adding the pkg-cyrus-sasl2 mailing list to the cc list) > What is the status of the adoption of the package? We have some work committed to our SVN repository, but it's not yet in a state where we can start trying to build other packages against it. We also have to think about the upgrade process and there have been several requests for a code audit (to weed out concurrency bugs, more than a security audit). > Not that I want to maintain it myself, but I would like to know if > you've already worked on #336485 and whether you intend to upload a > fixed package soon (be it by lowering the priority or switching to a > more recent libdb). We will switch to a newer bdb. Whether it will be 4.3 or 4.4 remains to be seen. (The safe approach being 4.3 of course.) > As part of the current BSP, we may have a look at the bug, if you're not > working on it. Or maybe you already have hints. The bug itself seems to be fairly trivial as it doesn't include any code changes if you just lower the priority and rebuild. Switching libdb would mean more work as you'd have to test with the newer libdb. I would personally go for not switching libdb in the "old" package and instead concentrate all efforts on getting the new package out. -- Fabian Fagerholm <fabbe@debian.org>
Attachment:
signature.asc
Description: This is a digitally signed message part