Merge ~sergiodj/ubuntu/+source/sssd:merge-2.4.1-2-impish into ubuntu/+source/sssd:debian/sid

This is the merge of sssd 2.4.1-2 from Debian.

First, the good news. Upstream and Debian have both adopted a change that I proposed during last cycle, which means that we're now able to drop some of our delta.

Here's a rundown of what we're dropping:

- d/p/condition-path-exists-sssd-conf.patch and d/p/0003-Only-start-sssd.service-if-there-s-a-configuration-f.patch: Used to make sssd.service start only if there is a configuration file present. I submitted an upstream patch which was accepted.

- d/p/lp-1908065-01-syslog_identifier-format.patch and d/p/lp-1908065-02-remove-syslog_identifier.patch: Used to remove custom SYSLOG_IDENTIFIER from journald, which was cluttering the logs and making them hard to read. This was a backport from upstream, which is now not needed.

During the merge process I also found a problem with the Python tests which affects only Ubuntu. The fix can be considered a general improvement, so I submitted it upstream here:

https://github.com/SSSD/sssd/pull/5636

and I am also incorporating it into our delta.

Now, the not-so-good news. There is another test failing: fail_over-tests. I spent some time debugging it and trying to understand what exactly is happening, but was unable to get to the bottom of the problem (I didn't want to spend too much time on it, since I have other things on my plate). I was able to determine that the problem seems to be related to libtevent, because the failure happens when "tevent_loop_once" is invoked. What's curious is that this failure only happens inside a chroot (when using sbuild, or when building the package on Launchpad, for example), and doesn't manifest on Debian. In all other scenarios the test passes, which tells me that this is probably sbuild/chroot-related and shouldn't impact regular users. For this reason, I am proposing that we temporarily disable this test. By the way, I got in touch with Timo (Debian's sssd maintainer) and he confirmed that he is aware of this issue but doesn't know why it happens.

As a side note, sssd has been recently re-enabled on i386 and you can check that it is currently not building there because of a missing dependency. I am already in contact with vorlon in order to get this sorted out; by the looks of it, it shouldn't be too much of a work.

There's a proposed PPA here:

https://launchpad.net/~sergiodj/+archive/ubuntu/sssd-merge/+packages

autopkgtest is still happy:

autopkgtest [18:32:44]: @@@@@@@@@@@@@@@@@@@@ summary
ldap-user-group-ldap-auth PASS
ldap-user-group-krb5-auth PASS