In this commit: https://git.yoctoproject.org/poky/commit/?h=master-next&id=7603fbafe39f78d850dc0ad590eace4d2edda6e4 Richard asked: "Would upstream accept a configure option?" Discuss this with upstream and if there's agreement then re-write the change as a configuration option.
Hi Randy, The link seem to be broken, Can you share more details?
Hi Dixit, master-next links come and go. Thanks for asking for a better link. You can search using lore, like this: https://lore.kernel.org/openembedded-core/?q=shadow-native%3A+Disable+syslog+usage+f%3Apurdie The commit log I was referring to is: https://lore.kernel.org/openembedded-core/20250228101323.1008021-1-richard.purdie@linuxfoundation.org/ Subject: [PATCH] shadow-native: Disable syslog usage Spamming the build host's syslog with useradd information during image creation isn't great. Add a patch to disable that. It may be possible to convince upstream to make it a configure option but for now the patch is trivial and reduces host impact to the logs. Does that help?
Thanks Randy, I will go through it.
Move to 6.0. Dixit, any news?
This completely went out of sight. I shall get on this right away. I also have one more item pending 12904, it's done from my end, pending acceptance(couple of review cycles done). If you could take a look and get this going. Thanks, Dixit
Hi everyone. Opened an issue on shadow-maint https://github.com/shadow-maint/shadow/issues/1610
Fixed by https://patchwork.yoctoproject.org/project/oe-core/patch/20260507121434.63608-1-frezidok1@gmail.com/
https://git.openembedded.org/openembedded-core/commit/?h=master&id=b0ce3150e43cb6fb0d726cf86725715b8fd06147 I never trust or properly parse the patchwork links. It does indicate that the patch is Accepted so I guess either link is sufficient proof. Thanks Dmitry.