Missing autoconf build-dependancy in cyrus-imapd-2.3 branch ?

[Sven Mueller]

Duncan Gibb schrieb:
>> https://mail.incase.de/svn/cyrus22/branches/cyrus23/cyrus-imapd-2.3-development/", 
> 
> JP> When trying to "dpkg-buildpackage", it complained about
> JP> missing autoconf :
> 
> Yes; sorry about that.  Henrique has suggested previously that the
> autotooling could be improved in several specific ways.  Maybe you
> should open a bug against cyrus-imapd-2.3 so I don't forget again...
> 
> 
> JP> Out of curiosity : what about pushing those packages to the
> JP> experimental or untable branch ?
> 
> We'd probably get away with the current branch in experimental, but a
> bit more release engineering will be required before we upload to Sid, I
> think...

At least in one regard it seems we don't need to do much. I took some
time today to start developing a script which would upgrade all
BerkeleyDB-Files as needed. Point is: At least from the currently used
4.2 to 4.6 (which seems to be the most recent version in unstable), a
db4.6_upgrade on a 4.2 db file reports a successful upgrade without
changing a single byte of the db file. So in this special case, we
wouldn't need to do anything at all, it seems, except perhaps to
automatically change the cyrus-db-types.active file to reflect the
now-used BerkeleyDB engine.

Regards,
Sven