Right - looking at the testcases:
> Certificate 42655A75156B3DE0 does not contain key
> 94706F8DA571389E8642BDFD42655A75156B3DE0 or it is not valid
Says right there, the backend doesn't know FAIL/NOKEY either because, like I
assumed, it's not possible to differentiate the two. So scratch the "ideally"
above, this is just a FAIL but the Sequoia error message makes it clear it can
be one of the two things.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3334#issuecomment-2429018076
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3334/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
