Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Clarify license for Debian packaging

See original GitHub issue

Currently I am working on creating Debian package for pylama ( However, the content of pylama/ is confused. The comment string says it is BSD license, but the LICENSE file is LGPL-3+.

Code audit tool for python.
:copyright: 2013 by Kirill Klenov.
:license: BSD, see LICENSE for more details.

__version__ = "7.0.9"
__project__ = "pylama"
__author__ = "Kirill Klenov <>"
__license__ = "GNU LGPL"

Please help to clarify the actual license of this package by removing other license name/text in pylama so that we can work on Debian packaging, thanks.

<bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](** We accept bounties via [Bountysource]( </bountysource-plugin>

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:1
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

susamcommented, Aug 15, 2018

Here are the commit history details regarding the licensing terms:

  • Commit f6f4aab6 (2012-08-17) is the initial commit that shows that the project was originally licensed under GNU LGPL.
  • Commits b1b10d14 (2013-05-21), 868b5337 (2013-06-06) and dcb35e46 (2013-08-07) mention BSD license.
  • Commit a6ce4655 (2013-06-06) shows the intention of moving from GNU LGPL to BSD license.
  • Commit 4f13f63a (2014-06-30) mentions GNU LGPL in the classifiers metadata.

In the latest master branch (at commit c38d598):

  • Files LICENSE and mention GNU LGPL only.
  • Files docs/index.rst, pylama/libs/, and README.rst mention BSD license only.
  • File pylama/ mentions both BSD license and GNU LGPL.

The project was originally licensed under GNU LGPL but later the author appears to have an intention of moving to BSD license. While there are several commits that provide evidence in favour of this conclusion, commit 4f13f63a contradicts this conclusion. The only place in the project that attempts to communicate the license explicitly to users or readers is README.rst which mentions:

Licensed under a BSD license.

It is unclear which BSD license (BSD-3-Clause or BSD-2-Clause) is meant here.

Here is Debian’s interpretation of the licensing terms (quoting from /usr/share/doc/pylama/copyright of Debian GNU/Linux 9 (stretch)):

Upstream-Name: pylama

Files:     *
Copyright: 2013 copyright Kirill Klenov <>
License:   LGPL-3+

Files:     pylama/
Copyright: 2013 copyright Kirill Klenov <>
License:   LGPL-3+ or BSD-3-clause

Files:     pylama/libs/
Copyright: 2013 copyright Kirill Klenov <>
License:   BSD-3-clause

Files:     debian/*
Copyright: ChangZhuo Chen (陳昌倬) <>
License:   LGPL-3+
klencommented, Nov 25, 2021

From the version 8.0.0+ Pylama has the MIT license.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Machine-readable debian/copyright file
This file is one of the most important files in Debian packaging, ... and a copyleft license, License can be used to clarify...
Read more >
Debian packaging ... is licensed under the GPL version 3 in ...
1 Answer 1 ... Debian packages often combine multiple projects into one package. The copyright file typically contains very accurate descriptions ...
Read more >
ubuntu - copyright file in deb package - how to - Stack Overflow
if you build a package using low-level tools like dpkg-deb you should have a good knowledge on the internals of a debian package....
Read more >
2. Basic Overview of the debian/ Directory - Packaging Guide
This article will briefly explain the different files important to the packaging of Ubuntu packages which are contained in the debian/ directory.
Read more >
Third Party Notices and/or Licenses - Oracle Help Center
This is the Debian prepackaged version of the GNU diffutils package. ... License but for only such changes as are necessary in order...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found