Re: [PATCH] bluez5: upgrade 5.72 -> 5.76

["Guðni Már Gilbert" <gudni.m.g@gmail.com>]

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

On Sun, Jul 7, 2024 at 10:00 AM, Richard Purdie wrote:

> 
> Thanks for the patch, unfortunately this ran into issues in our CI. One
> interesting one is this:
> 
> https://valkyrie.yoctoproject.org/#/builders/40/builds/65
> https://valkyrie.yoctoproject.org/#/builders/36/builds/64/steps/17/logs/stdio
> 
> 
> which isn't very clear what is going on until you look at the files:
> 
> (buildbot-venv) [pokybuild@rocky9-vk-1 ~]$ ls
> /home/pokybuild/yocto-worker/qemuarm-oecore/build/build/tmp-glibc/work/qemuarm-oe-linux-gnueabi/core-image-sato/1.0/testimage-sdk/sysroots/cortexa15t2hf-neon-oe-linux-gnueabi/etc/bluetooth/
> -la
> total 32
> dr-xr-xr-x. 2 pokybuild pokybuild 4096 Jul 7 11:11 .
> drwxr-xr-x. 3 pokybuild pokybuild 4096 Jul 7 11:26 ..
> -rw-r--r--. 1 pokybuild pokybuild 928 Jul 7 11:11 input.conf
> -rw-r--r--. 1 pokybuild pokybuild 12597 Jul 7 11:11 main.conf
> -rw-r--r--. 1 pokybuild pokybuild 120 Jul 7 11:11 network.conf
> 
> The missing write bit on the directory is stopping the files from being
> deleted.

Thanks for the report
I looked again at what changed between BlueZ 5.72 and 5.76 and found this (see image). The permission bits for /etc/bluetooth are explicitly set to 555 now. I suppose we would want 755 so that the 'owner' can write.

Two ideas to move this issue forward:
1) Send a patch to propose changing 555 to 755 for /etc/bluetooth and create a v2 of this upgrade. (The upstream status f or 0004-configure.ac-Fix-disable-cups.patch can also be updated at the same time since I sent the patch upstream)
2) Somehow modify the permission bits during the Yocto build (do_install perhaps?)

For the musl issue I found this in the logs:

I'm not very familiar with musl but my understanding is this compiler warning is being treated as an error? Is this correct behavior?

Gudni

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