I'm will jwakely. I sync my db between multiple devices, some of which don't have an option for v2 databases. I'm all for having 2.0.0 available, but if it can't read/write v1 databases, put it in a new package instead of unceremoniously breaking existing, long-standing functionality.
Keepassx was released in F23 as keepassx-0.4.3-13.fc23.x86_64 but then later upgraded to keepassx-2.0.0-1.fc23. The latter uses a different database format which is incompatible. I have tried version locking it but gnome software ignores the version lock and updates it. This database is shared among multiple users with multiple distros so I cannot just convert to the newer database format.
BZ#1282825 update keepassx to 2.0.0 (was: KeePassX 2.0 is coming!)
This update has been submitted for testing by frafra.
Works for me, imported with no issues.
This update has been pushed to testing.
Just imported my old databse, updated some passwords and saved it without any issues.
This update has been submitted for stable by bodhi.
works for me, lost "recents" history, import of v1 db went fine
This update has been pushed to stable.
Works for me. I can open and modify my .kdbx files (from KeePass). I can now replace KeePass/Mono with KeePassX. Thank you.
This is an incompatible change on a release branch that requires irreversible changes to the database.
I'm will jwakely. I sync my db between multiple devices, some of which don't have an option for v2 databases. I'm all for having 2.0.0 available, but if it can't read/write v1 databases, put it in a new package instead of unceremoniously breaking existing, long-standing functionality.
Backwards-incompatible change to a stable release.
This update was an ugly surprise and breaks the update-policy. Please provide a keepass-v1 package besides this one.
Keepassx was released in F23 as keepassx-0.4.3-13.fc23.x86_64 but then later upgraded to keepassx-2.0.0-1.fc23. The latter uses a different database format which is incompatible. I have tried version locking it but gnome software ignores the version lock and updates it. This database is shared among multiple users with multiple distros so I cannot just convert to the newer database format.
breaks update policy.....
That compatibility break is a no go for me