Hi On 1/25/26 16:23, Simon McVittie wrote:
So I think the only thing that gdm3 could do to resolve this bug would be to drop the test coverage that tries to detect/avoid regressions when configured to do smart card authentication using sssd, leaving those code paths untested. (Concretely, that would mean dropping "sssd-gdm- smartcard-auth-test", leaving only "greeter".) Is that what the release team wants?
autopkgtest on amd64 and arm64 that fail in testing are already RC for years, albeit not much bugs have been filed with that argumentation. Regressions of tests in testing have been RC on all release architectures [1], again, not a lot of bugs have been filed for that reason. Despite the lack of bug reports, it does mean that packages in testing shouldn't test depend on something that isn't in testing. We should get better in preventing removal of test dependencies, I started that discussion some time ago [2], except nothing materialized out of that yet.
If sssd seems a lost cause (I somehow doubt that the current situation is that, there's quite some activity upstream) than it would be best to drop the sssd test in gdm3. As you're all volunteers I can't say how to spend your time, but maybe helping sssd maintainers to fix the issue is better time spend than removing the test (albeit that might be quicker). Once the test is removed, I suspect it might be forgotten to be added back once sssd is in testing again.
Paul [1] https://release.debian.org/testing/rc_policy.txt paragraph 6a. [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=145257#163
OpenPGP_signature.asc
Description: OpenPGP digital signature
