Please upload to unstable.

[Henrique de Moraes Holschuh]

On Wed, 01 Nov 2006, Luk Claes wrote:
> If you all agree that the version in experimental is not suitable for release,
> then can you please make sure that the current package in unstable gets
> updated with the most important fixes, TIA?

This is essentially impossible to do right, most of the good stuff is
upstream changes.  Getting what we have in experimental good for release is
a far better use of time :(

And sincerely, if all that it takes is to REVERT the BDB upgrade, why don't
we do that and upload to unstable?   SASL gains very, very little from BDB
newer than 3.2 -- and that's if the local admin *knows* how to do BDB DBA
work using the db#.#_* stuff, because SASL certainly doesn't (unlike Cyrus
IMAP and OpenLDAP).

And we are NOT sure SASL works right with BDB 4.4, either.  Nobody checked
the API chages with a fine comb, AFAIK.  Just so you don't get away thinking
it is safe to do this with berkeley db, Cyrus IMAPd 2.3 upstream had rare
data stream corruptions (that hosed LMTP completely when they happened)
because of BDB 4.3->4.4 that were noticed and fixed less than two months
ago.  In the BDB 4.2->4.3 days, there were bad pointer derreferences because
of BDB API changes (fortunately, it affected errors going to syslog() only,
and not user data).

Please revert SASL to BDB 4.2 and let's upload to unstable.

-- 
  "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
  Henrique Holschuh