This is a great application for storing your passwords. In our repo we have the old KeePassX, and also the semi-old KeePassX2 Description of problem: No update - not even security - for over a year. Also their forum is down, so it seem unmaintained. For that reason, the project have already forked a while ago, to https://keepassxc.org/project , see https://keepassxc.org/docs#faq-keepassx I suggest we switch to that maintained version for security as well as options; add KeePassXC any time now, and omit KeePassX and KeePassX2 in mga7 ? KeePassXC use the KeePass2 database format as its native file format, and like KeePassX2 it can import KeePass (.kdb) database.
(In reply to Morgan Leijström from comment #0) > This is a great application for storing your passwords. > In our repo we have the old KeePassX, and also the semi-old KeePassX2 > > Description of problem: > No update - not even security - for over a year. > Also their forum is down, so it seem unmaintained. > For that reason, the project have already forked a while ago, to > https://keepassxc.org/project , see https://keepassxc.org/docs#faq-keepassx > > I suggest we switch to that maintained version for security as well as > options; > add KeePassXC any time now, and omit KeePassX and KeePassX2 in mga7 ? Hi Morgan, keepassxc was imported into Mga7 cauldron by sander85, and wally already made it obsolete keepassx2. I guess you've seen that, since you set the version of this report to Mageia 6.... I suppose you are requesting a backport? Anyway, assigning to Sander for the request to let keepassxc obsolete keepassx, too.
Status comment: (none) => (Version cauldron for the obsolete keepassx request)Source RPM: keepassx-0.4.4-1.mga6.src.rpm => keepassxcCC: (none) => marja11Assignee: bugsquad => mageia
Ah great :) Uh, I forgot to check Cauldron, sorry. Have not had time to follow development for quite a while and forgot procedures... My main concern is already taken care of then. I think it is *not* a good idea to let it replace keepassx1 *automatically* as the database upgrade is one way, and some users may need to keep using old format for compatibility reasons if they sync with an with an old device(i have been in that situation). Or what happens with the mga6>7 upgrade if keepassx1 is kept...? In any case we must note it in the release notes. As for backporting, that is a good idea - at least I would definitely switch. (i was thinking on switching my old keepassx to keepassx2 when i discovered keepassxc.) IF KeePassX2 is perfectly upgradeable to KeePassXC it may even be released as an update...? From the change log since KeePassX2 it really looks just like continued bugfix and development, see https://github.com/keepassxreboot/keepassxc/wiki/KeePassXC-Changelog (but that page is not updated since april... where is the rest?)
I'll think about the backport when I have more free time in hand.
KeepassXC is now in Mageia 7 keepassxc-2.4.1-1.mga7 And Mageia 6 is EOL. Thus closing.
Resolution: (none) => FIXEDCC: (none) => yves.brungard_mageiaStatus: NEW => RESOLVED
I forgot about this bug. Been using KeepassXC in mga7 long time now. Thank you :)