Skip to content

Review request: python-pyjaspar

I find the copyright info a bit difficult. The init.py keeps the copyright from Biopython, but the rest is GPL from how I interpret it. I requested upstream to clarify the situation.

Review for package python-pyjaspar

Link to the pipeline run: https://salsa.debian.org/med-team/python-pyjaspar/-/pipelines

The package uses debhelper and is lintian-clean

This checklist assumes the above to ensure that some points of the Policy such as rules on when copyright files can be symbolic links, etc., are respected. If for some reason you accept to reveiw a package that can not use these tools, read again Policy 12.5 very carefully and check all the points manually.

The debian/copyright file contains:

  • A statement where the upstream sources were obtained (Policy 12.5§3).
  • A name or contact address (email, forum, bugtracker, …) for the upstream authors (individuals or organisations) (Policy 12.5§3).
  • The names of all copyright holders.
    • the copyright-grep CI test can help you for text files.
    • the file-types CI test can help you finding binary files that may contain copyright statements, such as images, PDFs, etc..
  • Year information for the copyright statements ([Jaspert-2006]).
  • A license statement for the packaging work in debian/ ([Jaspert-2006]).
  • No extra information that belong to README files (Policy 12.5§8).
  • A verbatim copy of the licenses (Policy 2.3§1, 12.5§1), with the following exception:
  • For the Apache license (version 2.0), the Artistic license, the Creative Commons CC0-1.0 license, the GNU GPL (1, 2, or 3), the GNU LGPL (2, 2.1, or 3), the GNU FDL (1.2 or 1.3), and the Mozilla Public License (1.1 or 2.0), refer to the corresponding files under /usr/share/common-licenses, instead fully quoting (Policy 12.5§7), and include the appropriate header ([Jaspert-2006][]).