Hi, Jonathan Wakely <[email protected]> writes:
> Has something changed in rpminspect recently? I built a new dejagnu > package and it's failing rpminspect: > https://artifacts.dev.testing-farm.io/d6ffbc34-995f-47a5-b41a-87b5ff33be0d/ > The error is: > "/usr/share/dejagnu/remote.exp is not a valid sh script on noarch" > > and ... well, that's true. It's not a sh script at all. It's not > executable, it doesn't have a shebang, it doesn't end in .sh ... why > is rpminspect even looking at it? I suspect this is the reason why: https://github.com/rpminspect/rpminspect/pull/1412 rpminspect sees that the remote.exp file has a mime-type beginning with `text/`, then sees that it contains `exec sh...` so the heuristic it uses concludes that the script itself is an `sh` script. > A build a few weeks ago didn't have this problem. Fedora's CI was using a stale version of rpmisnpect for a while, so maybe that's why this started showing up now? Omair -- PGP Key: B157A9F0 (http://pgp.mit.edu/) Fingerprint = 9DB5 2F0B FD3E C239 E108 E7BD DF99 7AF8 B157 A9F0 -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
