[Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71

[Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71

[Davis Mosenkovs]

Changelog:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

Removed patch which is included in this release.
---
 .../bluez5_utils-headers.mk                   |  2 +-
 .../0001-configure-Check-ell-path.patch       | 35 -------------------
 package/bluez5_utils/bluez5_utils.hash        |  2 +-
 package/bluez5_utils/bluez5_utils.mk          |  4 +--
 4 files changed, 3 insertions(+), 40 deletions(-)
 delete mode 100644 package/bluez5_utils/0001-configure-Check-ell-path.patch

diff --git a/package/bluez5_utils-headers/bluez5_utils-headers.mk b/package/bluez5_utils-headers/bluez5_utils-headers.mk
index 0790dd7e0e..03c3ab9287 100644
--- a/package/bluez5_utils-headers/bluez5_utils-headers.mk
+++ b/package/bluez5_utils-headers/bluez5_utils-headers.mk
@@ -5,7 +5,7 @@
 ################################################################################
 
 # Keep the version and patches in sync with bluez5_utils
-BLUEZ5_UTILS_HEADERS_VERSION = 5.68
+BLUEZ5_UTILS_HEADERS_VERSION = 5.71
 BLUEZ5_UTILS_HEADERS_SOURCE = bluez-$(BLUEZ5_UTILS_VERSION).tar.xz
 BLUEZ5_UTILS_HEADERS_SITE = $(BR2_KERNEL_MIRROR)/linux/bluetooth
 BLUEZ5_UTILS_HEADERS_DL_SUBDIR = bluez5_utils
diff --git a/package/bluez5_utils/0001-configure-Check-ell-path.patch b/package/bluez5_utils/0001-configure-Check-ell-path.patch
deleted file mode 100644
index 3e5f7c6516..0000000000
--- a/package/bluez5_utils/0001-configure-Check-ell-path.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From 124187ef9abed60a7c40f751153e9c4516cd1f91 Mon Sep 17 00:00:00 2001
-From: Rudi Heitbaum <rudi@heitbaum.com>
-Date: Sat, 1 Jul 2023 01:31:20 +0000
-Subject: [PATCH] configure: Check ell path
-
-Use of AC_CHECK_FILE prevents cross compilation.
-Instead use test to support cross compiling.
-
-Signed-off-by: Rudi Heitbaum <rudi@heitbaum.com>
-
-Upstream: https://github.com/bluez/bluez/pull/546
-
-Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
----
- configure.ac | 7 ++++---
- 1 file changed, 4 insertions(+), 3 deletions(-)
-
-diff --git a/configure.ac b/configure.ac
-index eff297960..bc7edfcd3 100644
---- a/configure.ac
-+++ b/configure.ac
-@@ -298,9 +298,10 @@ if (test "${enable_external_ell}" = "yes"); then
- 	AC_SUBST(ELL_LIBS)
- fi
- if (test "${enable_external_ell}" != "yes"); then
--	AC_CHECK_FILE(${srcdir}/ell/ell.h, dummy=yes,
--			AC_CHECK_FILE(${srcdir}/../ell/ell/ell.h, dummy=yes,
--				AC_MSG_ERROR(ELL source is required or use --enable-external-ell)))
-+	if (test ! -f ${srcdir}/ell/ell.h) &&
-+			(test ! -f ${srcdir}/../ell/ell/ell.h); then
-+				AC_MSG_ERROR(ELL source is required or use --enable-external-ell)
-+	fi
- fi
- AM_CONDITIONAL(EXTERNAL_ELL, test "${enable_external_ell}" = "yes" ||
- 				(test "${enable_btpclient}" != "yes" &&
diff --git a/package/bluez5_utils/bluez5_utils.hash b/package/bluez5_utils/bluez5_utils.hash
index 45952e60f1..7d0fa980bc 100644
--- a/package/bluez5_utils/bluez5_utils.hash
+++ b/package/bluez5_utils/bluez5_utils.hash
@@ -1,5 +1,5 @@
 # From https://www.kernel.org/pub/linux/bluetooth/sha256sums.asc:
-sha256  fc505e6445cb579a55cacee6821fe70d633921522043d322b696de0a175ff933  bluez-5.68.tar.xz
+sha256  b828d418c93ced1f55b616fb5482cf01537440bfb34fbda1a564f3ece94735d8  bluez-5.71.tar.xz
 # Locally computed
 sha256  b499eddebda05a8859e32b820a64577d91f1de2b52efa2a1575a2cb4000bc259  COPYING
 sha256  ec60b993835e2c6b79e6d9226345f4e614e686eb57dc13b6420c15a33a8996e5  COPYING.LIB
diff --git a/package/bluez5_utils/bluez5_utils.mk b/package/bluez5_utils/bluez5_utils.mk
index 82800c0430..5f8811d6bd 100644
--- a/package/bluez5_utils/bluez5_utils.mk
+++ b/package/bluez5_utils/bluez5_utils.mk
@@ -5,12 +5,10 @@
 ################################################################################
 
 # Keep the version and patches in sync with bluez5_utils-headers
-BLUEZ5_UTILS_VERSION = 5.68
+BLUEZ5_UTILS_VERSION = 5.71
 BLUEZ5_UTILS_SOURCE = bluez-$(BLUEZ5_UTILS_VERSION).tar.xz
 BLUEZ5_UTILS_SITE = $(BR2_KERNEL_MIRROR)/linux/bluetooth
 BLUEZ5_UTILS_INSTALL_STAGING = YES
-# 0001-configure-Check-ell-path.patch
-BLUEZ5_UTILS_AUTORECONF = YES
 BLUEZ5_UTILS_LICENSE = GPL-2.0+, LGPL-2.1+
 BLUEZ5_UTILS_LICENSE_FILES = COPYING COPYING.LIB
 BLUEZ5_UTILS_CPE_ID_VENDOR = bluez
-- 
2.43.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71

[Thomas Petazzoni via buildroot]

Hello Davis,

On Mon, 18 Dec 2023 20:32:30 +0200
Davis Mosenkovs <davikovs@gmail.com> wrote:

> Changelog:
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog
> 
> Removed patch which is included in this release.

Thanks a lot for this patch! From a quick look, it looks good. However,
there is a silly, but important issue that prevents applying your
patch: it lacks your Signed-off-by line. Could you resend your patch
with this added at the end of your commit message?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71

[Davis]

Hello!

Can somebody who understands the legal side better sign off this change?
I sent the patch as discussed here
https://lists.buildroot.org/pipermail/buildroot/2023-December/681118.html
The patch itself (the few build configuration lines it adds) was
created by me in my spare time and I submit it under Buildroot's
license (GPL 2 or later).

Br,
Davis


trešd., 2023. g. 20. dec., plkst. 22:24 — lietotājs Thomas Petazzoni
(<thomas.petazzoni@bootlin.com>) rakstīja:
>
> Hello Davis,
>
> On Mon, 18 Dec 2023 20:32:30 +0200
> Davis Mosenkovs <davikovs@gmail.com> wrote:
>
> > Changelog:
> > https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog
> >
> > Removed patch which is included in this release.
>
> Thanks a lot for this patch! From a quick look, it looks good. However,
> there is a silly, but important issue that prevents applying your
> patch: it lacks your Signed-off-by line. Could you resend your patch
> with this added at the end of your commit message?
>
> Thanks a lot!
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71

[Thomas Petazzoni via buildroot]

Hello Davis,

On Thu, 21 Dec 2023 01:31:28 +0200
Davis <davikovs@gmail.com> wrote:

> Can somebody who understands the legal side better sign off this change?
> I sent the patch as discussed here
> https://lists.buildroot.org/pipermail/buildroot/2023-December/681118.html
> The patch itself (the few build configuration lines it adds) was
> created by me in my spare time and I submit it under Buildroot's
> license (GPL 2 or later).

Then, you are able to add your Signed-off-by at the end of your commit
message, and resubmit the patch, that's all what's needed.

Look at all other patches posted to the list, it will show you an
example of what the Signed-off-by line should look like.

There is also a great deal of information on how to submit patches to
Buildroot in our documentation at:
https://buildroot.org/downloads/manual/manual.html#submitting-patches

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71

[Davis]

[-- Attachment #1.1: Type: text/plain, Size: 1433 bytes --]

Hello Thomas,

Thank you!

Just one more question, BlueZ itself is covered by a license that allows
persons not affiliated with BlueZ or Buildroot to bump the package version,
correct?

Best regards,
Davis

ceturtd., 2023. g. 21. dec., plkst. 09:42 — lietotājs Thomas Petazzoni (<
thomas.petazzoni@bootlin.com>) rakstīja:

> Hello Davis,
>
> On Thu, 21 Dec 2023 01:31:28 +0200
> Davis <davikovs@gmail.com> wrote:
>
> > Can somebody who understands the legal side better sign off this change?
> > I sent the patch as discussed here
> >
> https://lists.buildroot.org/pipermail/buildroot/2023-December/681118.html
> > The patch itself (the few build configuration lines it adds) was
> > created by me in my spare time and I submit it under Buildroot's
> > license (GPL 2 or later).
>
> Then, you are able to add your Signed-off-by at the end of your commit
> message, and resubmit the patch, that's all what's needed.
>
> Look at all other patches posted to the list, it will show you an
> example of what the Signed-off-by line should look like.
>
> There is also a great deal of information on how to submit patches to
> Buildroot in our documentation at:
> https://buildroot.org/downloads/manual/manual.html#submitting-patches
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com
>

[-- Attachment #1.2: Type: text/html, Size: 2248 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71

[Thomas Petazzoni via buildroot]

Hello Davis,

On Fri, 22 Dec 2023 00:41:23 +0200
Davis <davikovs@gmail.com> wrote:

> Just one more question, BlueZ itself is covered by a license that allows
> persons not affiliated with BlueZ or Buildroot to bump the package version,
> correct?

I don't even see how the license of a software could prevent that. And
"affiliated with BlueZ or Buildroot" has absolutely no legal meaning.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71

[Peter Korsgaard]

>>>>> "Davis" == Davis  <davikovs@gmail.com> writes:

 > Hello Thomas,
 > Thank you!

 > Just one more question, BlueZ itself is covered by a license that allows
 > persons not affiliated with BlueZ or Buildroot to bump the package version,
 > correct?

Yes. I am not aware of any license having such restrictions (and we
would not be able to carry such package in Buildroot then).

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot