I looked at this a bit more, here are some findings: - the "module-init-tools" package is returned from cache.get_changes() *but* it not marked for install/remove/upgrade/reinstall/downgrade - funny enough its also not marked "keep" so its in some heisenstate - module-init-tools is not installable because it has a hard depenency on libkmod2=21-1ubuntu1 but the libmod2 version in xenial is 22-1ubuntu1. - when apts depcache.cc sees a package like module-init-tools that has a hard dependency that can't be satisfied it will reset the candidate version. I (strongly) suspect it also need to set it back into "keep" state.
So to fix this we need: - make module-init-tools installable again - fix apt to not go into heisenstate when it encounters a situation like this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550741 Title: Upgrade failed - unauthenticated package (module-init-tools) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/module-init-tools/+bug/1550741/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
