During a recent security MRE of clamav (1.5.3 IIRC), the security team requested that the changes be uploaded separately rather than be included in the MRE.
Currently the PRs on this bug for J/N contain the still needed fix, as well as the follow-up fix to address the point that Andreas had raised. Since the fix (without the patch to Andreas' concern) was merged while Resolute was -devel, Stonking and Resolute are fixed with respect to this bug, but still had the duplicate daemon-reload call. After discussions in Matrix I opened up a follow-up bug [1] to address just the follow-up fix. The subsequent fix was then merged into Stonking. So currently Jammy and Noble are blocked on sponsorship/upload of the follow-up fix at [1] to Resolute. The path forward would be to sponsor the Resolute MR on [1] and then the remaining MRs on this bug. [1] https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2160988 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2129160 Title: [FFe] [SRU] dpkg-reconfigure clamav-daemon does not respect TCP configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2129160/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
