On Wed, Oct 17, 2018 at 09:22:35PM +0300, Niko Tyni wrote: > > As a status update, I count just six packages left in testing that are > marked as blockers for this bug. (I could be wrong of course; double > checking welcome.)
I think you missed one. > - src:foolscap #898800: foolscap: FTBFS against openssl 1.1.1 I'm not sure if this is actually still a problem, there have been fixes on the python and openssl side for this. reproducible builds shows it as having problems trying to install the build dependencies for months. > - src:kdeconnect #907339: qtbase-opensource-src breaks kdeconnect autopkgtest > possibly due to new openssl > - src:kimap #907427: (kimap) openssl 1.1.1 breaks ssl tests There is also purpose, they all seem to be related to qtbase-opensource-src. > - src:ruby-eventmachine #900160: ruby-eventmachine: FTBFS against openssl > 1.1.1 I'm not sure why the patch didn't fix it > - src:python-boto #909545: SSL CERTIFICATE_VERIFY_FAILED when using gs > (Google Cloud Storage) backend Patch is available. > - src:m2crypto #897658: m2crypto: FTBFS against openssl 1.1.1 Only test suite problems that don't show any real issues. > Is it still useful to block openssl 1.1.1 testing migration with this bug? Things like python are also blocked on it. I have no problem lowering the severity of this issue, to make it migrate. Kurt
