Control: tags -1 moreinfo Hi Sebastian, On 08-06-2019 00:35, Sebastian Andrzej Siewior wrote: > Please unblock package openssl. > The updated package is the `c' version, which is the latest upstream > release for the 1.1.1 series. > This update causes a regresion in the m2crypto test suite which is > tracked as #929903. The regression is fixed upstream and I plan to > provide an update. > There is also a minor report valgrind report about an unitialized > memory tracked as #930061. This one will be fixed in the next upload > because it is not serious enough to cherry-pick the patch right away. > > unblock openssl/1.1.1c-1 Can you please elaborate why this version meets the freeze policy, or why it should get an exception? In the text above there is no mention at all of serious bugs that get fixed. openssl is a rather important package and we don't want to risk of regression this late in the release so we are *very* reluctant to have new upstream releases. Please help us make the right judgment call. Even if we were to unblock, can we get the m2crypto fix available, such that they can migrate together? I understood (last time I checked that bug) that this may just be a test fix? Paul
Attachment:
signature.asc
Description: OpenPGP digital signature