Bug 281904
| Summary: | devel/py-libvirt: Update to 10.8.0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | mew14930xvi <mew14930xvi> | ||||
| Component: | Individual Port(s) | Assignee: | Roman Bogorodskiy <novel> | ||||
| Status: | New --- | ||||||
| Severity: | Affects Only Me | CC: | ronald | ||||
| Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(novel) |
||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| URL: | https://gitlab.com/libvirt/libvirt-python/-/commits/master/ | ||||||
| Attachments: |
|
||||||
This issue looks like a duplicate of bug #281590. Although the patch in this issue also contains a license change. The port in git claims LGPL3 which is already different of what the patch of this issue tries to change. (In reply to Ronald Klop from comment #1) Oh my mistake. It is libvirt vs py-libvirt. So no duplicate issue. But py-libvirt is already version 10.9.0 in git also. Only the license change of this issue is left. https://www.freshports.org/devel/py-libvirt License seems a little tricky. The COPYING file specifies LGPL 2.1. libvirt-python.spec specifies LGPL-2.1-or-later. setup.cfg specifies "License :: OSI Approved :: GNU Lesser General Public License v2 or later (LGPLv2+)" which I assume also technically equal to 2.1+ as pypi doesn't have a separate LGPL 2.1 classier. Some header files also specify 2.1 or later. So I guess LGPL21+ would be a more accurate choice. |
Created attachment 254057 [details] update to 10.8.0