Hi Ravi, OpenSSL gets a lot of security updates. We need some way to test if the patches we add to this package break it or not. While just blindly adding the resolute patches to this package may work for a while, as soon as we hit a snag and it stops building or working properly because of the different dependencies and toolchains in stonking+, we won't have the command line tools to run autopkgtests, or our test scripts.
We either never update it for security issues, which is less than ideal, though perhaps acceptable since it is only used for graphics drivers, or we have the packaging provide the openssl binary in a different filesystem location so it can be called by autopkgtest and test scripts, like the openssl1.0 package did. The openssl1.0 package provided the openssl binary in /usr/lib/ssl1.0/openssl, so something similar could be done here, like /usr/lib/ssl3.5/openssl. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167636 Title: create an openssl3-compat package for stonking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2167636/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
