Bug 46249 - Possibly incorrect packaging of licenses
Summary: Possibly incorrect packaging of licenses
Status: NEW
Alias: None
Product: Sisyphus
Classification: Development
Component: pve-common (show other bugs)
Version: unstable
Hardware: all Linux
: P5 normal
Assignee: Andrew Vasilyev
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-24 18:53 MSK by Leonid Krivoshein
Modified: 2023-05-24 19:02 MSK (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leonid Krivoshein 2023-05-24 18:53:41 MSK
In https://bugzilla.proxmox.com/show_bug.cgi?id=4737#c4
Fabian Grünbichler wrote:

I'll give a few examples, but these are just taken at random, and in no way meant as indication that I audited your usage of the code in question or any other packages and that everything not mentioned is compliant!

pve-common: your package metadata says it's GPLv3 licensed, while it is AGPL-3.0 or later
pve-docs(-generator): licensed under GFDL, patched very crudely, not following section 4 of the license
pve-manager: licensed under AGPL-3.0 or later (our code), patched, section 5 of AGPL 3.0 not followed

in addition to this, almost all the packages provided by you don't ship our license information and copyright statement(s) - they are contained in the (debian/)"copyright" file in both our git repositories and the resulting binary packages we distribute, but are not shipped by your binary packages AFAICT (I am not an rpm expert, so it is possible I misinterpret something here).

last (but not least), you cannot add any restriction like "legal entities can use it for testing but production use requires acquiring licenses or signing a license agreement in written form." on AGPL licensed software, neither on the original one written by us, nor on your patched version.