Hi Alessandro and thanks for this bug report. This is the kind of fix that can be backported to existing stable releases using the SRU process [1]. Given that every change comes with a regression risk, the most important ingredient of a SRU is the broken use case that the proposed upgrade fixes, see [3]. This is missing in both this bug report and in the upstream commit [3] message you pointed us to (thanks!).
Could you please provide more information about the problem that [3] fixes, describing the broken use case? Steps to reproduce the broken scenario are normally the best explanation.
Waiting for your reply I'm marking this bug report as Incomplete.
Hi Alessandro and thanks for this bug report. This is the kind of fix that can be backported to existing stable releases using the SRU process [1]. Given that every change comes with a regression risk, the most important ingredient of a SRU is the broken use case that the proposed upgrade fixes, see [3]. This is missing in both this bug report and in the upstream commit [3] message you pointed us to (thanks!).
Could you please provide more information about the problem that [3] fixes, describing the broken use case? Steps to reproduce the broken scenario are normally the best explanation.
Waiting for your reply I'm marking this bug report as Incomplete.
[1] https:/ /wiki.ubuntu. com/StableRelea seUpdates /wiki.ubuntu. com/StableRelea seUpdates# When /github. com/net- snmp/net- snmp/commit/ 78bf0069ddd24ea 0cc716421c53e1d af46da7002
[2] https:/
[3] https:/