The issue has been fixed upstream, in version 1.0.5 already AFAICT. Unless there are reasons for z-streaming the fix, I'd suggest we rebase the package in RHEL9 to get this implicitly fixed as well.