From: "Guðni Már Gilbert" <gudni.m.g@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bluez5: upgrade 5.72 -> 5.76
Date: Sun, 07 Jul 2024 05:55:46 -0700 [thread overview]
Message-ID: <20061.1720356946240260660@lists.openembedded.org> (raw)
In-Reply-To: <bdc48d97eea594eff799a370fc66fb28f283de52.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1505 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.
I wonder if this resolves the issue, looks exactly like something we need: https://docs.python.org/3/library/shutil.html#rmtree-example
( https://docs.python.org/3/library/shutil.html#rmtree-example ) There's a comment in the Bitbake code saying rmtree is too slow, but that's from 12 years ago. Perhaps it is fast enough today with Python 3.12.
I don't think the solution is to request BlueZ to change how it installs it's files/directory.
[-- Attachment #2: Type: text/html, Size: 1833 bytes --]
next prev parent reply other threads:[~2024-07-07 12:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 23:56 [PATCH] bluez5: upgrade 5.72 -> 5.76 Guðni Már Gilbert
2024-07-04 0:01 ` Guðni Már Gilbert
2024-07-04 9:44 ` [OE-core] " Alexander Kanavin
2024-07-04 10:50 ` Guðni Már Gilbert
2024-07-04 10:53 ` [OE-core] " Alexander Kanavin
2024-07-05 8:46 ` Guðni Már Gilbert
2024-07-07 10:00 ` [OE-core] " Richard Purdie
2024-07-07 10:38 ` Guðni Már Gilbert
2024-07-07 10:41 ` Guðni Már Gilbert
2024-07-07 11:30 ` Guðni Már Gilbert
2024-07-08 8:15 ` [OE-core] " Richard Purdie
2024-07-08 21:02 ` Guðni Már Gilbert
2024-07-08 22:56 ` Guðni Már Gilbert
2024-07-09 10:38 ` [OE-core] " Richard Purdie
2024-07-07 12:55 ` Guðni Már Gilbert [this message]
2024-07-08 8:14 ` Richard Purdie
2024-07-09 14:01 ` Alexandre Belloni
2024-07-09 17:13 ` 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=20061.1720356946240260660@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.