From: Leo Famulari <leo@famulari.name>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 27909@debbugs.gnu.org
Subject: [bug#27909] Replace keepassx with keepassxc
Date: Tue, 1 Aug 2017 17:12:39 -0400 [thread overview]
Message-ID: <20170801211239.GA5844@jasmine.lan> (raw)
In-Reply-To: <20170801201150.GQ2406@macbook42.flashner.co.il>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
On Tue, Aug 01, 2017 at 11:11:50PM +0300, Efraim Flashner wrote:
> On Tue, Aug 01, 2017 at 03:43:19PM -0400, Leo Famulari wrote:
> > The last keepassx release was in October 2016. That's not *that* long
> > unless there are some serious bugs in the program.
>
> The maintainer is MIA. I'm not aware of serious bugs, other than it
> still relying on Qt-4.
Ah, still using Qt-4 is my pet peeve! :) That means it will have to be
removed sooner or later.
> > Are other distros replacing keepassx?
> >
>
> I don't believe Debian is, but there is active work on packaging
> keepassxc. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855173
>
> > Is keepassxc a "seamless" replacement for keepassx, or would users maybe
> > have to adjust somehow?
>
> It is supposed to be a seamless replacement, using the same .kdbx files
> as keepassx.
Okay, I'll defer to what others think, especially since I'm not using
keepass*.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-01 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 15:08 [bug#27909] Replace keepassx with keepassxc Efraim Flashner
2017-08-01 19:43 ` Leo Famulari
2017-08-01 20:11 ` Efraim Flashner
[not found] ` <CAFtzXzNLwfPYKMH17x1Lijhgevjr0-DvxBBw31QP6tYnNBUExg@mail.gmail.com>
[not found] ` <CAFtzXzMoODFaqFjApZLHBZiQ+eHJ0qun71k7qpinX2rfXpdxug@mail.gmail.com>
2017-08-01 20:27 ` Manolis Ragkousis
2017-08-01 21:17 ` Leo Famulari
2017-08-02 18:28 ` Manolis Ragkousis
2017-08-01 21:12 ` Leo Famulari [this message]
2017-08-16 15:10 ` bug#27909: " Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170801211239.GA5844@jasmine.lan \
--to=leo@famulari.name \
--cc=27909@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.