Comment 6 for bug 1982218

Revision history for this message
Nick Rosbrook (enr0n) wrote :

Thanks for that additional information.

So, looking into this a bit, I am a bit tempted to just drop this patch from Jammy. For one, I will be dropping this patch in the current cycle because upstream has a patch[1] now that accomplishes the same goal in a different way.

More importantly though, looking at bug 1728181 (for which this patch exists), it's not clear to me that this ever worked exactly as it was intended. I will follow up to try and find out what happened, but based on the comments it sounds like the fix was incomplete and wasn't further developed.

Testing on Lunar, this patch only works as intended when the --any flag is specified, which I think is because when this patch was refreshed over the years, it was not correctly adapted for the context.

TL;DR - I do think this is something we can address in the next Jammy SRU, and AFAICT just dropping the patch should solve your issue.

[1]