pkg/32738: db4 upgrade to 4.4 breaks 4.3-based apps like cyrus-imapd

[John Kohl <jtk%kolvir.arlington.ma.us@localhost>]

>Number:         32738
>Category:       pkg
>Synopsis:       db4 upgrade to 4.4 breaks 4.3-based apps like cyrus-imapd
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Feb 04 23:30:01 +0000 2006
>Originator:     John Kohl
>Release:        NetBSD 3.0
>Organization:
NetBSD Kernel Hackers `R` Us
>Environment:
System: NetBSD desktop.john.kohl.name 3.0 NetBSD 3.0 (KOLVIR-$Revision: 1.64 $) 
#7: Sat Jan 21 15:58:30 EST 2006 
jtk%desktop.john.kohl.name@localhost:/u4/sandbox/src/sys/arch/i386/compile/KOLVIR
 i386
Architecture: i386
Machine: i386
>Description:
I rebuilt all my packages for NetBSD 3.0 using the latest version of
packages (no branch).
Switching from db4-4.3.29
to db4-4.4.16
results in failures in cyrus-imapd.

Is db 4.4 incompatible with 4.3-formatted databases?  If it's supposed
to be compatible, it's not and there's a bug somewhere.

If it's supposed to be incompatible, do we need to keep old & new
packages around (support multiple db4 releases)?

How about an upgrade/conversion guide?

>How-To-Repeat:
build cyrus-imapd & db4-4.3.29 on NetBSD-2.1, install them & use them
build cyrus-imapd & db4-4.4.16 on NetBSD-3.0.
upgrade the packages
restart cyrus
see this in your log file:
Feb  4 17:43:39 kolvir ctl_cyrusdb[22717]: DBERROR  (^F^H: db4
Feb  4 17:43:39 kolvir ctl_cyrusdb[22717]: DBERROR  (^F^H: db4
Feb  4 17:43:39 kolvir ctl_cyrusdb[22717]: recovering cyrus databases
Feb  4 17:43:39 kolvir ctl_cyrusdb[22717]: skiplist: recovered 
/var/imap/mailboxes.db (24 records, 3232 bytes) in 0 seconds
Feb  4 17:43:39 kolvir ctl_cyrusdb[22717]: skiplist: recovered 
/var/imap/annotations.db (0 records, 144 bytes) in 0 seconds
Feb  4 17:43:39 kolvir ctl_cyrusdb[22717]: DBERROR  (^F^H: db4
Feb  4 17:43:39 kolvir ctl_cyrusdb[22717]: DBERROR  (^F^H: db4
Feb  4 17:43:39 kolvir ctl_cyrusdb[22717]: DBERROR: critical database situation
Feb  4 17:43:39 kolvir master[584]: process 22717 exited, status 75 
Feb  4 17:43:39 kolvir master[584]: servname not supported for ai_socktype, 
disabling sieve
Feb  4 17:43:39 kolvir master[584]: ready for work
Feb  4 17:43:39 kolvir ctl_cyrusdb[16218]: DBERROR  (^F^H: db4
Feb  4 17:43:39 kolvir ctl_cyrusdb[16218]: DBERROR: critical database situation
Feb  4 17:43:46 kolvir imap[22685]: DBERROR ^T^Z        ^H: db4
Feb  4 17:43:46 kolvir imap[22685]: DBERROR: critical database situation
Feb  4 17:43:46 kolvir master[584]: service imap pid 22685 in READY state: 
terminated abnormally
Feb  4 17:43:46 kolvir imap[23095]: DBERROR ^T^Z        ^H: db4
Feb  4 17:43:46 kolvir imap[23095]: DBERROR: critical database situation
Feb  4 17:43:46 kolvir master[584]: service imap pid 23095 in READY state: 
terminated abnormally
Feb  4 17:43:46 kolvir imap[25526]: DBERROR ^T^Z        ^H: db4
Feb  4 17:43:46 kolvir imap[25526]: DBERROR: critical database situation
Feb  4 17:43:46 kolvir master[584]: service imap pid 25526 in READY state: 
terminated abnormally
Feb  4 17:43:46 kolvir imap[7885]: DBERROR ^T^Z ^H: db4
Feb  4 17:43:46 kolvir imap[7885]: DBERROR: critical database situation
Feb  4 17:43:46 kolvir master[584]: service imap pid 7885 in READY state: 
terminated abnormally

>Fix:
        revert to 4.3.29, built on NetBSD-3.0.