http://qa.mandrakesoft.com/show_bug.cgi?id=2411
------- Additional Comments From [EMAIL PROTECTED] 2003-02-26 06:14 ------- Running dbconverter-2 without user intervention is quite easy: echo | dbconverter-2 /source/db /target/db Okay, SASL v1 and v2 use a different format. Fine. When upgrading from a running system with v1 to v2, the user is left WITHOUT a database! So, users might fear that they've lost their SASL database. That's *VERY* bad. Because of this, I think it's MUCH better if the database is upgrade from v1 to v2, even if it can't be kept in sync by technical means. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: I updated from cyrus v1 to cyrus v2. During the ugrade, the existing sasl.db hasn't been upgraded to v2 with dbconverter-2 and it has been renamed to /var/lib/sasl.db.rpmsave. I'd expect the upgrade to also upgrade an existing sasl.db. As said, dbconverter-2 needs to be run. But that's impossible because of bug #2410.
