On Mon, 13 Jan 2025 at 14:07, POPESCU Catalin <[email protected]> wrote: > One easier way to address the issue with the bluez config files not > shipped on scarthgap would be to revert the actual commit that > introduced the issue : > > commit 49391fdcf71b32c5fd3c7b134c1d1c45cc1db388 > Author: Emil Kronborg <[email protected]> > Date: Thu Feb 22 19:44:59 2024 +0000 > > bluez5: remove configuration files from install task > > Since be0e796299b0 ("build: ship all config files with > --enable-datafiles") in bluez, installing input.conf and network.conf > has been redundant, as the bluez5 recipe already includes > --enable-datafiles. > > Signed-off-by: Emil Kronborg <[email protected]> > Signed-off-by: Richard Purdie <[email protected]> > > This commit should have never been merged as long as scarthgap pulls in > bluez 5.72 (The commit mentioned be0e796299b0 was merged in bluez 5.73 > not in 5.72).
That is correct. I'd like to clarify from Emil how this change came to be, as oe-core master had only 5.72 at that point, and bluez recipe was updated to a later release much later. You can send a revert for scarthgap, please write a commit message that carefully explains the issue. Reverts in LTS make people nervous. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#209785): https://lists.openembedded.org/g/openembedded-core/message/209785 Mute This Topic: https://lists.openembedded.org/mt/110494576/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
