On Thu, Jan 30, 2014 at 05:36:05PM +0100, Johannes Schlumberger wrote: > Hi Roberto, > thank you for looking into this. I will send you a link to the sasldb2 file > in a > personal separate email for you investigation (would you please provide me > with > an address?). Please keep the contents of this file private. You may share the > contents and the file with other package maintainers or who else you see fit > to > work on this bug, provided they also keep it private.
Johannes, I believe that I have figured out the problem. It appears that you created the sasldb2 file on a big endian machine and then later moved it to a little endian machine. This causes the upgrade to fail. Here is what happens on my amd64 system: roberto@miami:/var/lib/chroot/squeeze/etc$ sudo db5.1_upgrade sasldb2 db5.1_upgrade: sasldb2: DB->upgrade only supported on native byte-order systems db5.1_upgrade: DB->upgrade: sasldb2: Invalid argument roberto@miami:/var/lib/chroot/squeeze/etc$ file sasldb2 sasldb2: Berkeley DB (Hash, version 8, big-endian) I temporarily transferred the file over to a PowerPC porterbox, and here is what happens: (sid_powerpc-dchroot)roberto@partch:~$ db5.1_upgrade sasldb2 (sid_powerpc-dchroot)roberto@partch:~$ logout roberto@partch:~$ file sasldb2 sasldb2: Berkeley DB (Hash, version 9, native byte-order) Based on this, I believe that this is not a bug in the sasl2-bin package. I believe that you can correct this by dumping the contents using the db4.8_dump command and then recreating the database on your system. If you agree, I would like to close this bug report. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
