Hi Alex, I wanted to provide an update on this issue.
The proposed fix has now been accepted upstream by the gawk maintainer. The changes to randtest.sh have been reviewed and integrated into the upstream repository, with appropriate updates to the original file and test/ChangeLog. Given that the root cause has now been addressed upstream, this issue can be resolved in oe-core by backporting the corresponding upstream fix, rather than relying on a workaround such as skipping the test. Please let me know if you would like me to prepare a backport patch for oe-core based on the upstream changes. Thanks, Aditya On Thu, May 28, 2026, 11:03 AM Aditya G.S <[email protected]> wrote: > Hi Alex, > > Thanks for the guidance. > > A few days back I was facing SMTP configuration issues with git > send-email, which prevented me from sending patches in the proper format. > Because of that, I initially shared the patch manually. > > The SMTP issue is now resolved, and I have since used git send-email for > submissions. I also resent the patch to gawk upstream using git send-email, > addressing the bug-gawk mailing list and CC'ing the maintainers. > > Please let me know if anything further is needed from my side. > > Thanks, > Aditya > > On Wed, May 27, 2026, 5:36 PM Alexander Kanavin <[email protected]> > wrote: > >> On Wed, 27 May 2026 at 13:41, Aditya G.S <[email protected]> wrote: >> > At this point, I am waiting for his feedback on the proposed fix. Once >> I receive a response or the patch is accepted (or revised), I will follow >> up accordingly and share the upstream link when available. >> > >> > Please let me know if you would prefer that I proceed with a temporary >> Yocto-side workaround (such as skipping the test) while the upstream >> resolution is pending. >> >> Thanks for summarizing, but I think there's a standard mailing list >> archive, where emails are placed as soon as they're sent: >> >> https://lists.gnu.org/archive/html/bug-gawk/2026-05/msg00054.html >> >> I see you're struggling with sending attachments there, I'm not sure >> why you can't simply use 'git send-email' to send the patch, as you >> just did on this list, but that is typically much preferred. Email >> attachments are difficult to review, especially when line by line >> comments are needed. >> >> Otherwise, upstream seems friendly and responsive, so we should >> probably wait a bit? Ideally, they'd add the fix to the upstream git >> repo, and then it can be backported in oe-core. >> >> Alex >> >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#237734): https://lists.openembedded.org/g/openembedded-core/message/237734 Mute This Topic: https://lists.openembedded.org/mt/119495833/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
