JFTR cyrus-sasl2 should not fail with openssl 1.0, so I'll fix that quickly if needed.
O. -- Ondřej Surý <ond...@sury.org> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware, fast DNS(SEC) resolver Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro pečení chleba všeho druhu On Fri, Feb 3, 2017, at 13:45, Sebastian Andrzej Siewior wrote: > On 2017-02-01 22:18:07 [+0100], Sebastian Andrzej Siewior wrote: > > Currently I am rebuilding testing with the same set of package against > > libssl-dev provided by libssl1.0-dev. After that I retry the failed > > packages above where I am not sure why they failed (mostly I suspect the > > parallel) case. > > Do you want a complete testing rebuild or another set of packages? > > it is at [0] and a retry of all failed with -j1 at [1]. I had just a > quick look: > - perl fails in the test suite but that ist "okay". It builds against > 1.0 but it B-D are built against 1.1 and perl exposes the openssl ABI > as-is. So rebuilding it in the right order should avoid it. > > - a few packages like cfengine3, ldns, freelan, duo-unix, dogecoin, > dsniff and cyrus-sasl2 seem like they compile with 1.1 but do not > compile against 1.0 since they expect 1.1 functions to be around. > There may be more, I had a quick look. The build succeeded with 1.1 > earlier. > > - some of globus-* and lcmaps-* packages fail and I am not sure if they > can't deal with 1.0 anymore or if it is similar to perl where > everything has to be moved to 1.0 in the right order. > > [0] > https://breakpoint.cc/openssl-rebuild/2017-02-01-rebuild-testing-against-openssl1.0/ > [1] > https://breakpoint.cc/openssl-rebuild/2017-02-01-rebuild-testing-against-openssl1.0-retry/ > > > > Cheers, > > > Julien > > Sebastian