I found myself affected by this. I had 1:20.04.10.3 presumably because update-manager 1:20.04.10.5 is phased at 50%. Fixed manually:
Upgrade: update-manager-core:amd64 (1:20.04.10.3, 1:20.04.10.5), update-manager:amd64 (1:20.04.10.3, 1:20.04.10.5), python3-update-manager:amd64 (1:20.04.10.3, 1:20.04.10.5)
So the fix looks good to me too, and will be resolved for everyone when phasing hits 100%. Thanks!
I found myself affected by this. I had 1:20.04.10.3 presumably because update-manager 1:20.04.10.5 is phased at 50%. Fixed manually:
Upgrade: update- manager- core:amd64 (1:20.04.10.3, 1:20.04.10.5), update- manager: amd64 (1:20.04.10.3, 1:20.04.10.5), python3- update- manager: amd64 (1:20.04.10.3, 1:20.04.10.5)
So the fix looks good to me too, and will be resolved for everyone when phasing hits 100%. Thanks!