Will the build problem for Leap 15.1 or Leap 15.2 because of a not sufficient p11-kit version solved ? It would be also interesting if a sssd-kcm package (available since version 1.16) could be built for the new sssd release. Thanks for your infos !

Jan Engelhardt (jengelh) - over 4 years ago

maintainer

Not from my side. Yes.

---

Ralf Kölmel (koralle) - over 4 years ago

Thank you for the fast response and the building of the sssd-kcm package !

Is there a timeline for when 2.6.3 will be submitted to factory? Particularly, it addresses a major regression in AD authentication introduced in 2.6.2.

Jan Engelhardt (jengelh) - almost 3 years ago

maintainer

whenever they get their signature file right :-/

---

Samuel Cabrero (scabrero) - almost 3 years ago

maintainer

https://github.com/SSSD/sssd/releases/download/2.6.3/sssd-2.6.3.tar.gz.asc seems to be fine. But 2.6.3 release tarball is signed by Pavel's key and sssd.keyring only contains Alexey's key.

@jengelh, do you agree to add both keys to the keyring?

Hi! Are there any objections to adding --with-subid to the build options to enable support for https://github.com/SSSD/sssd/commit/f546088226872f24722bdd94388816792bd5891a ? If I am not mistaken, our version of shadow (v4.11.1) should already include support for it, as per https://github.com/shadow-maint/shadow/commit/8492dee6632e340dee76eee895c3e30877bebf45.

Can someone look at the builds for Leap and why it's looking for libldap-data 2.4 and openldap2 has been upgraded to 2.6?

Jan Engelhardt (jengelh) - about 2 months ago

maintainer

because the base system wants 2.4 and there is a certain forward incompatibility caused by the 2.4 package, yes we can workaround it, no this is not the place to submit bugs.