On 2026-10-05 17:14, Dave Cantrell via devel wrote:
OK, trying again. Accidently hit the hot key to send the message before
finishing it. As I was saying:
rpminspect is probably unable to match the product release string to a usable
filename. The linked MR is for an ELN build and the rpminspect-data-fedora
package contains no information about eln dist tags.
See:
https://codeberg.org/rpminspect/rpminspect-data-fedora/src/branch/main/fedora.yaml#L163
The regular expression is meant to map the dist tag to a key which ends up
being the filename used throughout the database, so like fileinfo/fc31.
There's nothing for ELN packages in the configuration and according to this:
https://artifacts.dev.testing-farm.io/ff272f10-9df0-4e35-9453-ada058a38907/
rpminspect is being passed "--release=eln159" which rpminspect takes as the
release string and then that doesn't map to a product definition in fedora.yaml, so there
are no fileinfo rules.
To fix this, someone needs to add an ELN product definition in fedora.yaml under
'products' and then add appropriate rules files throughout rpminspect-data-fedora. I
suggest calling the key 'eln' and then defining a regexp to match dist tags that begin
with ".eln".
Related question: Should ELN rpminspect use centos rules instead?
--
Miro Hrončok
--
Phone: +420777974800
--
_______________________________________________
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
