That's true. It's less than idea, but this allows those who need the old version to continue to do so, and I've submitted a review for a separate keepassx2 package: https://bugzilla.redhat.com/show_bug.cgi?id=1326875
If you need an f23 build, let me know the arch and I'll post one.
This update resulted into me locking myself out of an account and I suspect this will happen to many others.
Here is why and how that happened:
when transitioning to keepassx 2 I stored my password database into a new file: db2 (the old being "db1")
at some point in time I changed the password of the account (which got stored into db2)
the "update" to keepassx 0.4.4 happened without me noticing it
when I was about to login to my account I opened keepassx (0.4.4) which opened its distinct config and file "db1" (which contains the old - now changed password)
trigged multiple failed login attempts with the old password -> account locked
Keepassx is critical for many take maintenance more serious please.
This update has been submitted for testing by limb.
This update has been pushed to testing.
works for me
You cannot play with upgrades and downgrades since both database versions are NOT compatible
That's true. It's less than idea, but this allows those who need the old version to continue to do so, and I've submitted a review for a separate keepassx2 package: https://bugzilla.redhat.com/show_bug.cgi?id=1326875
If you need an f23 build, let me know the arch and I'll post one.
I am -1 for this update
I upgrade my database to the latest format and this versión can not open my current database format :(
https://bugzilla.redhat.com/show_bug.cgi?id=1329418
This update resulted into me locking myself out of an account and I suspect this will happen to many others.
Here is why and how that happened:
Keepassx is critical for many take maintenance more serious please.
Look Good to Me
This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
This update has been unpushed.