https://bugzilla.redhat.com/show_bug.cgi?id=2267321
--- Comment #18 from Dominik 'Rathann' Mierzejewski <dominik(a)greysector.net>
---
(In reply to Xavier Bachelot from comment #14)
Maybe missing an explicit BR: make rather than relying on deps ?
Good point, will add when importing.
Otherwise looks good, will try and do a full review asap.
Thanks!
(In reply to Xavier Bachelot from comment #17)
Could you please take a look at the following rpmlint warnings ?
librtmp.x86_64: W: crypto-policy-non-compliance-gnutls-2
/usr/lib64/librtmp.so.1 gnutls_priority_init
librtmp.x86_64: W: crypto-policy-non-compliance-gnutls-1
/usr/lib64/librtmp.so.1 gnutls_priority_set_direct
See
https://docs.fedoraproject.org/en-US/packaging-guidelines/CryptoPolicies/
And also :
librtmp.x86_64: W: binary-or-shlib-calls-gethostbyname
/usr/lib64/librtmp.so.1
Both shall probably at least be notified to upstream.
They are valid and I sent them upstream. However, I wonder if RTMP
even supports IPv6 or if there are specific old crypto
requirements at work here.
--
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2267321
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=rep...