https://bugzilla.redhat.com/show_bug.cgi?id=2316473



--- Comment #20 from Cristian Le <[email protected]> ---
Welp the tests are not exiting on error when they should be, e.g.:
```
test_strisalphanumeric_s 50   Error rc=1 
```
is reporting an error with:
https://github.com/intel/safestringlib/blob/fd159bf8c37a2a0b7ba328766f3c96d9aa075f27/unittests/test_strisalphanumeric_s.c#L45-L51

Maybe if upstream can back to us on those issues, try to ping them directly
about the test failures, it seems `dmwheel1` and `tomasbw` might be responsible
for the project.
At the same time, I've looked through the issues and one of the issues [1] is
recommending https://github.com/rurban/safeclib/ as an alternative as well. It
could also be an alternative and it shouldn't matter much which version is
actually used since the API are compatible (just the CMake code to consume it
will be different).

How about we try to contact the devs for both projects and ask their
recommendation on which version is more suitable for packaging. Either
`safestringlib` devs would come back and comment on the failing tests, or the
`safeclib` devs could offer some support for packaging that instead.

[1]: https://github.com/intel/safestringlib/issues/2


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2316473

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202316473%23c20

-- 
_______________________________________________
package-review 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://pagure.io/fedora-infrastructure/new_issue

Reply via email to