Bug#369882: cyrus-doc-2.2 upgrade issues [Recipes and Results]

[Ross Boylan]

On Wed, 2006-07-26 at 15:21 +0200, Sven Mueller wrote:
> Ross Boylan wrote on 26/07/2006 05:50:
> > By the way, I notice my entire active-types file is now just the line
> > DBENGINE BerkeleyDB4.2
> > 
> > Is that OK?
> > 
> > Even if it's OK, it's kind of an unfortunate loss of information: it
> > doesn't say what the database types are for the individual components.
> > This information was significant in the upgrade from 2.1, because it let
> > me see that many of my db's were already of the expected type, and so
> > didn't need conversion.
> 
> Like Benjamin already said, this is a known problem and fixed in SVN
> (and thus pending upload). However, that file only contains the
> information of the _default_ DB-types, it doesn't yet take into account
> what you configured in your imapd.conf file. In other words: If you
> reconfigure your Cyrus-IMAPd installation to only use skiplist or other
> non-BDB database types, you will still see BDB entries in that file.
> 
> I'm currently thinking of how to improve that. After all, even if
> Cyrus-IMAPd is linked against a newer BerkeleyDB, this shouldn't prevent
> it from starting if the local admin has configured his Cyrus IMAPd to
> run without any Berkeley databases.
> 
> Regards,
> Sven
If the file is at best duplicative of the info in imapd.conf and at
worst contradictory, maybe it should be deleted?  I had the impression
it was being used to determine the database types, and perhaps that was
a Debian thing in 2.1, which has now made it into upstream by a
different mechanism?