Comment 2 for bug 1788356

Hmm, I also am not able to reproduce this problem on other xenial systems.
Seems like the package lists were somehow broken.

I suppose xenial-updates was once activated and at some point was deactivated again. That would definitely explain the error.

-> can be closed