Thanks for the updates; your debdiff looks great and I will upload it, but:
Apologies for not catching this on the first round; it looks like this bug was introduced in SSSD 2.5.0 [1], so it would be present in Jammy & Noble too. Can you check to see if those releases are affected and if they are, prep debdiffs and check that the test plan works for them? Even if a user has only requested the fix for a newer release, we generally try to fix every affected release so that we don't have to do rework if someone is affected on an older release. One more feedback (for next time): even if the test plan exercises the affected codepath, that doesn't necessarily mean that the package still works when rebuilt (drift in the build dependencies, compiler bugs, etc). This risk is low (and even lower for sssd because it was rebuilt recently and has autopkgtest coverage), but it's still good to make sure in the test plan that the package still has its basic functionality. There are a few examples of breakage caused by rebuilds at [2]. Noting that autopkgtests cover this is often sufficient. [1] https://github.com/SSSD/sssd/commit/993b66d48d [2] https://ubuntu.com/project/docs/SRU/explanation/requirements/#minimal-changes-only -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2169162 Title: sssd-kcm fails to start due to use-after-free with krb5_renew_interval To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2169162/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
