On Sunday 30 March 2008 00:57, Murray S. Kucherawy wrote: > My (currently) preferred fix is attached. The only thing > DB_VERISON_CHECK(2,0,0) should be protecting is "flags". > > DB_UNKNOWN is preferred for the read-only case since in that instance the > database has already been created so selecting (or asserting) a database > mode isn't useful there. > > I changed the database type back to DB_HASH for back-compatibility. I had > decided DB_BTREE might be better for use with dkim-stats since then the > output would be automatically sorted, but back-compatibility is probably > more important.
I'd appreciate some advice on how to proceed from a distribution perspective. Ubuntu has a release coming up in a few weeks. Currently we are shipping 2.5.1 in the development release. My current thought is that we should update to 2.5.2 plus include this patch. Are there any other issues of significance that are open against 2.5.2 that have patches available? Scott K ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
