I was in the same situation for the Intrepid->Jaunty upgrade, with the jaunty repository pinned to priority 50. Arguably the situation improved, since the upgrade did not crash, but it only upgraded a limited number of packages (including the new kernel). Also after upgrade finished and after reboot it still offered upgrade to the new jaunty 9.04, as if upgrade wasn't registered.
Since it is sometimes necessary to upgrade selected packages to the next version, and pinning to a low priority is a convenient way to manage this mix, I think this situation is (relatively) frequent and it would be great if it could be handled more gracefully. It could be handled similarly to the third-party repositories, which are automatically disabled on upgrade. There should at least be a warning if /etc/apt/preferences is present, or the option to disable all pinning before starting the upgrade. -- Pinned hardy repository causes update-manger to fail but shows no error message https://bugs.launchpad.net/bugs/203659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
