Hello team,I'm the maintainer of libssh2 [1]. There was an old bug with this package asking to switch from libgcrypt to openssl [2].
The issue was with the license openssl that had consequences with its rdeps.The ftp-master team came up with a solution for the OpenSSL license [3]. This solution allows to use openssl in libssh2.
Therefore I uploaded a new package for libssh2 yesterday, hoping the libssh2-with-openssl package will be available for bullseye.
But because of the hard freeze, this has to be manually allowed.I recently added autopkgtests to the libssh2 package and try to maintain as clean as possible, but I'm aware this is a key package so changes may be potentially dangerous, especially before a release.
Therefore I'm asking your opinion on whether it would be wise to release libssh2-with-openssl in bullseye? The package uses libgcrypt for a long time now. And on second thought I wouldn't mind waiting another release for what could potentially break other packages.
Thanks in advance for your feedback /Nicolas [1] https://tracker.debian.org/pkg/libssh2 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668271[3] http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html
Attachment:
OpenPGP_0xFE82139440BD22B9.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature