On Wed, Aug 09, 2017 at 10:56:44AM +0200, Bas Zoetekouw wrote:
> Hi Julian,
>
> I was just about to file my own ITP for keepassxc when I stumpled upon
> yours.
>
> Could you give an update on the status? I'd be happy to help out with
> packaging and/or uploading, if you like.
debian/copyright needs an update and there's an embedded http
library that we might want to disable the feature using it.
I basically prepared the debian/copyright list of things to
add / change, but did not actually update it yet. Here's the
things that are different compared to COPYING (which also
lacks long licenses, but that's a different story):
[10:59:44] src/gui/csvImport/CsvParserModel.cpp contains Copyright
(C) 2016 Enrico Mariotti - but "Enrico" is not
mentioned anywhere
[11:01:33] cmake/CodeCoverage.cmake appears twice in there for some
reasons
[11:02:12] src/http Copyright (C) 2013 Francois Ferrand is missing
[11:03:47] qhttp/http-parser/LICENSE-MIT seems weird
[11:04:12] "Additional changes are licensed under the same terms as
NGINX and copyright Joyent, Inc. and other Node contributors. All rights
reserved."
[11:04:25] but then it lists an MIT license, so it's not clear what
that's supposed to mean
[11:04:52] Not to mention that "Igor Sysoev" does not appear anywhere
in COPYING
[11:08:27] src/keys has files Copyright (C) 2014 Kyle Manna
[11:10:35] src/totp is Apache licensed, effectively rendering the
entire program GPL-3. Not sure if that has any problem yet.
[11:11:08] several files are Copyright (C) 2017 Weslly Honorato
<wes...@protonmail.com>
[11:18:04] tests/TestDatabase.*: * Copyright (C) 2017 Vladimir
Svyatski
[11:22:11] tests/modeltest.*:** Copyright (C) 2015 The Qt Company Ltd
[11:23:12] I don't think you can just drop debfx's copyright
statement from copying and replace it with your own, though
[11:23:18] (at the top)
[11:25:38] The whole mac stuff by Lennart Gauer is not mentioned
anywhere
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.