Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Guðni Már Gilbert" <gudni.m.g@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Notes for BlueZ 5.80 upgrade
Date: Tue, 18 Mar 2025 01:24:58 -0700	[thread overview]
Message-ID: <RooI.1742286298693917560.s8EM@lists.openembedded.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

Hi all, in case this is useful, I want to share some notes for anyone who wants to upgrade BlueZ to 5.80 as I've been following upstream commits. My VM's SSD crashed recently such that I lost everything :(, so I can't really do the upgrade myself unless I set everything up again (not sure when that will happen).

Notes:
1) We should be able to remove the modifications to /etc/bluetooth directory permissions bits (done in do_install:append function) *[1]*. This was added previously for the SDK build so that uninstalling the directory/files works.
2) AMP code has been removed *[2]*. This means "tools/amptest" can be removed from NOINST_TOOLS_BT
3) One patch can be removed: 0001-gdbus-define-MAX_INPUT-for-musl.patch as it is included in the release now *[3]*
4) Upstream doesn't test musl builds... so anyone upgrading should test with musl also to pass all the checks :)

[1] - https://github.com/bluez/bluez/commit/b1fd409960001a77cda2a09ecc00147ebd9c3667
[2] - https://github.com/bluez/bluez/commit/1474c11618bc1092f7dd4b304d3768ce9da02b13
[3] - https://github.com/bluez/bluez/commit/9d69dba21f1e46b34cdd8ae27fec11d0803907ee

Best regards,
Gudni

[-- Attachment #2: Type: text/html, Size: 1760 bytes --]

             reply	other threads:[~2025-03-18  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  8:24 Guðni Már Gilbert [this message]
2025-03-22 17:34 ` Notes for BlueZ 5.80 upgrade Guðni Már Gilbert

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=RooI.1742286298693917560.s8EM@lists.openembedded.org \
    --to=gudni.m.g@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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