Skip to content

r-cran-multitaper/1.0-17-1

Review for package r-cran-multitaper/1.0-17-1

Stub to be developped.

I have read:

Copyright

  • All the copyright holders found by the copyright-grep CI test are mentionned in debian/copyright.
  • Files with embedded copyright statements (image metadata etc.) have been checked.
  • …

License

  • All licenses are mentionned in debian/copyright.
  • No license is unknown (if you have an unknown license, get it added to the list of known licenses).
  • The licenserecon pipeline reports no discrepancy.
    • licenserecon reports GPL instead of GPL-2+, because licensecheck could guess the version.
  • License terms reported in debian/copyright and not found in the upstream sources, must be documented about when and how the license information was obtained (for example download link, email correspondance, …) (REJECT-FAQ)
  • …

Source

  • Lintian did not report minified javascript
    • I could not yet manage to run the Salsa CI and the review CI at the same time…
  • …

Copyright file Policy requirements (2.3, 12.5)

The copyright file should contain:

  • 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).
  • For packages contrib or non-free: a statement that the package is not part of the Debian distribution and a brief explanation why (Policy 12.5§4).
  • 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 (versions 1, 2, or 3), the GNU LGPL (versions 2, 2.1, or 3), the GNU FDL (versions 1.2 or 1.3), and the Mozilla Public License (version 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).
  • A license statement for the packaging work in debian/ (Jaspert-2006).
  • The years of the copyright statements (Jaspert-2006).
  • No extra information that belong to README files (Policy 12.5§8).

File format, type and path.

  • /usr/share/doc/PACKAGE/copyright is neither compressed nor a symbolic link (Policy 12.5§1).
  • A verbatim copy of the package’s copyright information is often required to be present in /usr/share/doc/PACKAGE/copyright, too; see Copyright considerations.
  • The contents of the /usr/share/doc/PACKAGE/copyright files of the binary packages are available in debian/copyright in the source package (Policy 12.5$5).
  • All copyright files are encoded in UTF-8 (Policy 12.5§9).
  • The /usr/share/doc/PACKAGE/copyright files are always available: /usr/share/doc/PACKAGE can only be a symbolic link to /usr/share/doc/PACKAGE2/copyright if the two packages come from the same source and the first package Depends on the second.
Edited by Charles Plessy