Comment 8 for bug 1794478

> The new stable version indicate the fix mentioned by seb128 is there but no indication has been made in
> the debian/changelog to automatically change the status, which breaks the SRU machinery for this
> particular bug.

@Eric, I didn't handle it ine SRU because I don't understand the issue enough to be confident it's fixed in that update, I was just adding a side comment because the change looks like it could impact on the behaviour described there. Did you confirm the SRU does address the problem and that it's indeed fix commited? (and that it's really resolved in newer series)