Your message dated Mon, 18 Sep 2006 20:02:33 -0300
with message-id <[EMAIL PROTECTED]>
and subject line closing invalid bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: cyrus21-common
Version: 2.1.18-3
Severity: normal
when trying to import a mailboxes.db file from a redhat system I found
that the cvt_cyrusdb program is unable to create db3 databases.
the error is:
"Converting from /var/lib/cyrus-postillion/mailboxes.db.flat (flat) to
/var/lib/cyrus-postillion/mailboxes.db (db3-nosync)
fatal error: can't open new database"
and
"Converting from /var/lib/cyrus-postillion/mailboxes.db.flat (flat) to
/var/lib/cyrus-postillion/mailboxes.db (db3)
fatal error: can't open new database"
in syslog I found this error:
Aug 9 09:20:46 postillion2 cyrus/cvt_cyrusdb[6803]: DBERROR db3:
/var/lib/cyrus-postillion/mailboxes.db: unsupported btree version: 9
Aug 9 09:20:46 postillion2 cyrus/cvt_cyrusdb[6803]: DBERROR: opening
/var/lib/cyrus-postillion/mailboxes.db: Invalid argument
Aug 9 09:20:50 postillion2 cyrus/cvt_cyrusdb[6804]: DBERROR db3:
/var/lib/cyrus-postillion/mailboxes.db: unsupported btree version: 9
Aug 9 09:20:50 postillion2 cyrus/cvt_cyrusdb[6804]: DBERROR: opening
/var/lib/cyrus-postillion/mailboxes.db: Invalid argument
I have run ldd on cvt_cyrusdb and followed all the link in libs, they
all exist
This is preventing me from migrating all out fedora boxes to debian of
which there are some 20 out there. :(
This box was installed as etch I had to use some packages from unstable
(none of which are linked to this problem)
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages cyrus21-common depends on:
ii adduser 3.95 Add and remove users and groups
ii debconf [debcon 1.5.2 Debian configuration management sy
ii dpkg 1.13.21 package maintenance system for Deb
ii exim4-daemon-he 4.62-2 exim MTA (v4) daemon with extended
ii gawk 1:3.1.5.dfsg-4 GNU awk, a pattern scanning and pr
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libdb3 3.2.9+dfsg-0.1 Berkeley v3 Database Libraries [ru
ii libsasl2 2.1.19.dfsg1-0.2 Authentication abstraction library
ii libssl0.9.8 0.9.8b-2 SSL shared libraries
ii libwrap0 7.6.dbs-9 Wietse Venema's TCP wrappers libra
ii libzephyr3 2.1.20010518.SNAPSHOT-15 The original "Instant Message" sys
ii netbase 4.25 Basic TCP/IP networking system
ii perl 5.8.8-4 Larry Wall's Practical Extraction
Versions of packages cyrus21-common recommends:
ii cyrus21-imapd 2.1.18-3 Cyrus mail system (IMAP support)
-- debconf information:
cyrus21-common/warnbackendchange:
cyrus21-common/removespools: false
--- End Message ---
--- Begin Message ---
Agreed.
The error messages are pretty clear, the user is trying to do something we
simply don't support (and won't support in the 2.1 branch). His databases
are not in the same format as that expected by the berkeley DB used in
Debian Cyrus.
He needs to dump them to text in the source system, with the berkeley db
that was used to create the databases.
I am closing this bug.
--
"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
--- End Message ---
