Agree that it is spurious, now it worked for me. Not agree about the proposed reason. If it was a race with something independently accessing dpkg, it should happen more often, and during upgrade of an arbitrary package..
But both cases failed when upgrading apt or dpkg itself. So doesn't it look as if the running upgrade somehow locks itself out?
