Hello Arto,
please list these two files with their license separatlytest/ts-preset/fixture/package.json test/ts-preset-streaming/fixture/package.json Thanks
This looks like a false positive by the licenserecon tool that was used. The mentioned files are fake JSON definitions of typescript packages, used as test fixtures. A definition like that contains a "license" field that triggers the tool.
This is also a result of manual check.
These aren't real packages, there is no source code. As far as I understand these test fixtures have been written by the same author and are a part of the this package and if any copyright license applies to them (I'm not a lawyer but if I was and you'd pay me a couple of thousand dollars I'd tell you that they aren't copyrightable) it's the same one that applies to the rest of it (GPLv3+).
It is the task of the upstream author to define the preferred license.
I can of course easily add specific mentions of these files to the copyright file with a different license, but as far as I can tell that would make the information incorrect. Should I do that, or upload the package again as-is, or...?
After adding these files to d/copyright you can upload the package again. -- Mechtilde Stehmann ## Member of the DFSG, Licensing & New Packages Team ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
OpenPGP_signature.asc
Description: OpenPGP digital signature
