Bug 281904 - devel/py-libvirt: Update to 10.8.0
Summary: devel/py-libvirt: Update to 10.8.0
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Roman Bogorodskiy
URL: https://gitlab.com/libvirt/libvirt-py...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-06 18:21 UTC by mew14930xvi
Modified: 2024-11-19 17:12 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (novel)

Attachments
update to 10.8.0 (1.12 KB, patch)
2024-10-06 18:21 UTC, mew14930xvi 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mew14930xvi 2024-10-06 18:21:46 UTC 
Created attachment 254057 [details]
update to 10.8.0
Comment 1 Ronald Klop freebsd_committer freebsd_triage 2024-11-15 11:15:08 UTC 
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.
Comment 2 Ronald Klop freebsd_committer freebsd_triage 2024-11-15 11:19:30 UTC 
(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
Comment 3 Roman Bogorodskiy freebsd_committer freebsd_triage 2024-11-19 17:12:06 UTC 
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.