You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the freeradius build is separate from the new openssl builds, which leads to a systematic problem of incompatibility between the former and the latter.
Is it possible, when updating the OpenSSL package, to automatically rebuild freeradius using the latest version of OpenSSL, even if freeradius itself has not been updated?
This problem does not arise in the ARM branch of Arch Linux packages.
The text was updated successfully, but these errors were encountered:
We do have some semi-automation, but the problem is that a dependency of freeradius, namely yubico-c-client, is marked as broken. This stops any automation and a rebuild would be done on report after manual investigation.
I think we are still in need of more helping hands to speed up all sorts of small fix-ups to prevent this from happening ._.
It seems yubico-c-client is not developed anymore... It is now have a public archive status. As i see in official freeradius developer page, freeradius have only one dependency - libtalloc.
Is there a way to remove yubico-c-client from required dependency for freeradius?
Hello!
It seems that the freeradius build is separate from the new openssl builds, which leads to a systematic problem of incompatibility between the former and the latter.
Is it possible, when updating the OpenSSL package, to automatically rebuild freeradius using the latest version of OpenSSL, even if freeradius itself has not been updated?
This problem does not arise in the ARM branch of Arch Linux packages.
The text was updated successfully, but these errors were encountered: