Comment # 5 on bug 988273 from Ond��ej S��kup

(In reply to Egbert Eich from comment #4)
> (In reply to Ond��ej S��kup from comment #2)
> > @Egbert, SR#407423 for TW and SR#407424 for Leap:42.1 is workaround with
> > libnettle + update to 12.0.1 / 11.0.9
> > 
> > comment by Marek Olsak is clear : BTW, this is libcrypto developers' fault,
> > because they had changed their public interface, which is the cause of this
> > incompatibility.
> 
> WHich incompatibility?
> When the run time libs shipped by steam are not used 
> /lib/libcrypto.so.1.0.0 is used by both Mesa and steam. Where do you see an
> ABI breakage?

i think steam binary uses steamclient.so and steamservice.so with integrated
libcrypto into this two libraries ... and here might be incompactibility
between steam and Mesa used libs

> I would like the maintainer of openssl (where libcryto comes from) to look
> into this issue before we change anything in Mesa.
> 
> > and because steam isn't in our control ..
> 
> Of course not. But is this a valid reason to do kludge around this by
> adapting other packages?
> 
> I've declined the SRs for Mesa for now due to the change of crypto libs for
> now.
> I'd like to understand the issue better.
> I'm fine with the other updates.