Comment 6 for bug 1857036

Revision history for this message
Bryce Harrington (bryce) wrote :

Confirmed, I still was able to reproduce this on groovy with sudo 1.8.31-1ubuntu1, but groovy is now updated to 1.9.0-1ubuntu1 and now the behavior is correct.

From the bug report mentioned in comment #3, I found the commit with the corresponding patch.

I've added a focal bug task and marked the groovy one fixed. Although it's just a warning, it's pretty noticeable and could cause confusion so I think an SRU may be warranted.