Package: sssd
Version: 2.4.1-2
Severity: important

Dear Maintainer,

SSSD on bullseye remains broken even after #991274 and #994879. SSSD (2.5.2-3) 
supposedly fixes the issue, but the bullseye repo is held to an older, broken 
version.

I'm not sure how this old version works with LDAP in any scenario, as it 
expects libldap to support CLDAP (without falling back to LDAP) and debian 
libldap isn't compiled with CLDAP support.

Are we expected to install the newer .deb (outside of the repo) and/or compile 
libldap with CLDAP support? If we're expected to use the fixed version, please 
advise on the best practice for doing so. Or is it possible to add SSSD to 
bullseye-backports instead?

Thanks

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-15-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sssd depends on:
ii  python3-sss  2.4.1-2
ii  sssd-ad      2.4.1-2
ii  sssd-common  2.4.1-2
ii  sssd-ipa     2.4.1-2
ii  sssd-krb5    2.4.1-2
ii  sssd-ldap    2.4.1-2
ii  sssd-proxy   2.4.1-2

sssd recommends no packages.

sssd suggests no packages.

-- no debconf information

Reply via email to