Bug#855173: ITP: keepassxc -- Community fork of KeePassX, a free and open-source cross-platform password manager.
Hello!
KeePassXC Team here.
Thanks for taking ownership and helping us getting into Debian repository.
About the copyright, you can take the COPYING file in the root directory
of KeePassXC, it's updated and already in debian format. It's only
missing the full licenses.
Another little thing, I've seen that in the man page file it still says
keepassx. You can take this man page that is more updated
[https://github.com/magkopian/keepassxc-debian/blob/master/keepassxc-2.2.0/debian/keepassxc.1]
If you need anything you can ask us here or on IRC (freenode
#keepassxc-dev).
-TheZero
Il 28/06/2017 09:23, Julian Andres Klode ha scritto:
> Control: owner -1 !
>
> On Wed, Jun 28, 2017 at 09:04:16AM +0200, Julian Andres Klode wrote:
>> On Tue, Feb 14, 2017 at 05:51:25PM -0500, Matt Jones wrote:
>>> I am not a maintainer or developer but an active user if debain and
>>> keepass. I would be willing to take this in depending on timeframe. I have
>>> time starting next week to devote to this. I have built packages in the
>>> past so this is not a huge issue for me
>> So, are you still interested in this? I have a package mostly ready
>> (have not checked copyright and watch yet), it was really only a matter
>> of cloning the keepassx repo and then running sed s#keepassx#keepassxc#g
>> basically.
>>
>> If I don't hear from you in the next days, I assume you lost interest,
>> and will upload the package (and push it to a collab-maint/keepassxc.git
>> repo, you are of course free to join).
> The email bounced (address does not exist), and given that it's been 4 months
> since Matt tried to ITP, and he did not answer to the query 2 months ago, it's
> safe to assume he lost interest, so I'm taking ownership.
>
> I pushed the packaging so far to
> https://anonscm.debian.org/git/collab-maint/keepassxc.git
> (web ui will appear soon, and it might need some cleanup and rebasing
> before release; also copyright file needs update).
>
Reply to: