On 2016-12-05 22:36:39 [+0100], László Böszörményi (GCS) wrote: > Hi Sebastian, Hi László,
> On Mon, Dec 5, 2016 at 10:20 PM, Sebastian Andrzej Siewior > > Okay. What do we do here? Any idea Laszlo? > > I could try to cherry-pick the three patches into the currect 2.0 but I > > can't look at them because the git server seems to be down at the moment. > I'm a bit confused to be honest. Upstream has a note that SX support > (or the entire SX) is closed down. Do you want to RM: it? I just want to get the ssl part fixed somehow. > Edwin, does it mean that SX is no longer developed? > > Upstream asked about packaging 2.3 which makes sense (I think) but there > > is something regarding the update path If I read this correctly. And 2.3 > > works with openssl 1.1 but needs to go via NEW due to libsxclient4 and I > > hope this "transition" is okay because libsxclient3 has no rdeps. > I've packaged SX 2.3 and it looks fine - the upgrade path needs > testing. I had a plan to do it in a virtual machine (don't want to > hurt my real data), but then I didn't have time. Now I'm on holidays > for three days - I may need to go home sooner, but I can share the > packaging then. Okay. I don't want to be pushy here. If you want me to NMU it with the SSL patches applied please say so. Otherwise I will wait for you to get 2.3 uploaded. > Regards, > Laszlo/GCS Sebastian
