From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] package/python-paho-mqtt: clarify license information
Date: Mon, 20 Jul 2026 22:13:19 +0200 [thread overview]
Message-ID: <20260720201616.2EB148907B@busybox.osuosl.org> (raw)
commit: https://gitlab.com/buildroot.org/buildroot/-/commit/cbd7cb094f50b359563ef0948c1760cfa7a76f0d
branch: https://gitlab.com/buildroot.org/buildroot/-/tree/master
package/python-paho-mqtt is dual-licensed, so licenses should be
connected by "or". EDL v1.0 is a BSD-3-Clause license, as confirmed by
the ESF [1] (see listed SPDX License Identifier), also confirmed as
intended in the pyproject.toml file [2].
[1] https://www.eclipse.org/org/documents/edl-v10/
[2] https://github.com/eclipse-paho/paho.mqtt.python/blob/af64a4365c6ac5a7a4d339e7b00f44df91353b35/pyproject.toml#L10-L12
Signed-off-by: Fiona Klute (Othermo GmbH) <fiona.klute@gmx.de>
Signed-off-by: Julien Olivain <ju.o@free.fr>
---
package/python-paho-mqtt/python-paho-mqtt.mk | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/python-paho-mqtt/python-paho-mqtt.mk b/package/python-paho-mqtt/python-paho-mqtt.mk
index 90ed8370f7..5e1d2fe32d 100644
--- a/package/python-paho-mqtt/python-paho-mqtt.mk
+++ b/package/python-paho-mqtt/python-paho-mqtt.mk
@@ -6,7 +6,8 @@
PYTHON_PAHO_MQTT_VERSION = 2.1.0
PYTHON_PAHO_MQTT_SITE = $(call github,eclipse,paho.mqtt.python,v$(PYTHON_PAHO_MQTT_VERSION))
-PYTHON_PAHO_MQTT_LICENSE = EPL-2.0, EDLv1.0
+# LICENSE.txt, EDLv1.0 is a BSD-3-Clause license
+PYTHON_PAHO_MQTT_LICENSE = EPL-2.0 or BSD-3-Clause
PYTHON_PAHO_MQTT_LICENSE_FILES = LICENSE.txt epl-v20 edl-v10
PYTHON_PAHO_MQTT_SETUP_TYPE = hatch
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2026-07-20 20:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260720201616.2EB148907B@busybox.osuosl.org \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox