On Tue, Jan 12, 2016 at 10:41:24AM +0000, Jonathan Wakely wrote: > I'm concerned by this update too. > > The latest post in Bugzilla says: > > (In reply to Francesco Frassinelli (frafra) from comment #35) > >(In reply to Ed Marshall from comment #33) > >> (and, obviously, send email to the mailing list, so users are > >> actually > >> notified this time rather than getting a surprise breaking upgrade > >> out of > >> the blue) > > > >I can't downgrade keepassx because many people upgraded their > >database > >(comment #34). > > Those people are presumably happy with version 2 (or are stuck with it > now). But there are other people refusing to upgrade because of this. > > A possible solution is to include both keepassx-0.4.4 and > keepassx2-2.0.0 in F22 and F23, so people can choose which version to > use based on their preference (and whether they've already upgraded > their databases). > > >I could provide a keepassx2 subpackage which replaces keepassx = > >2.0.0, but > >I'm not sure about how to handle Obsoletes/Provides in this case. > > Couldn't both be installed at the same time (if the binaries are > renamed)? You just can't use the same .kdb file with both versions. Given that people have already had their databases upgraded to .kdbx (but the v1 .kdb file is still there), instead of downgrading keepassx which is now at v2, you could inroduce a new keepassx1 package. It might be cleaner that way now that the v2 package has already gone out. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
