This update breaks the updates policy. It is a non-essential major version update which makes irreversible changes to the DB format, preventing the same file being used by old clients.
Changing the major version was not needed because upstream are still providing security support for the old version "for some time".
However, now that the change has already been pushed to F23 arguably it's better to change F22 as well, to at least allow DB files to be shared between F22 and F23 machines.
I don't want to be forced to update all password-databases. I use those on other systems too. So at least do not update this in current Fedora versions (it breaks the update policy) In F24 I would suggest to provide the option to install the 1.x version besides the 2.0 version. (Version 1.x is still supported, b.t.w.)
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.
Update works, but this is disrubtive update.
This update breaks the updates policy. It is a non-essential major version update which makes irreversible changes to the DB format, preventing the same file being used by old clients. Changing the major version was not needed because upstream are still providing security support for the old version "for some time". However, now that the change has already been pushed to F23 arguably it's better to change F22 as well, to at least allow DB files to be shared between F22 and F23 machines.
Backwards-incompatible change to a stable release (the trailing stable release, at that).
I don't want to be forced to update all password-databases. I use those on other systems too. So at least do not update this in current Fedora versions (it breaks the update policy) In F24 I would suggest to provide the option to install the 1.x version besides the 2.0 version. (Version 1.x is still supported, b.t.w.)
This update has been obsoleted.
Definitely not a release that should go through.