The issue is that a newer version of shim-signed was installed than the version published in focal-updates, but your version of shim was older than the one in focal-updates, so a dist-upgrade forced removal of shim-signed and upgrade of shim.
This version of shim-signed was published to the focal release pocket prior to GA, so some users still have it on their system.
We should NOT have published shim-signed 1.40.4 with a lower version number than the highest version than had ever been in the focal release pocket.
I believe we need to rev the shim-signed SRU in focal to 1.41.1 to correct this issue, which is a separate one from apt choosing to remove shim-signed. Without this version fix, the other fix will never *reach* users of focal who are affected by this particular bug.
> Remove: shim-signed:amd64 (1.41+15+ 1552672080. a4a1fbe- 0ubuntu1)
The issue is that a newer version of shim-signed was installed than the version published in focal-updates, but your version of shim was older than the one in focal-updates, so a dist-upgrade forced removal of shim-signed and upgrade of shim.
https:/ /launchpad. net/ubuntu/ +source/ shim-signed/ 1.41/+publishin ghistory
This version of shim-signed was published to the focal release pocket prior to GA, so some users still have it on their system.
We should NOT have published shim-signed 1.40.4 with a lower version number than the highest version than had ever been in the focal release pocket.
I believe we need to rev the shim-signed SRU in focal to 1.41.1 to correct this issue, which is a separate one from apt choosing to remove shim-signed. Without this version fix, the other fix will never *reach* users of focal who are affected by this particular bug.