It seems that in the past it was the case that if one package source failed, then no updates would be executed by the update manager. I'm not certain if this issue has been fixed.
As regards the issue raised above, it does seem that simply disabling sources/PPA's after software is already installed is a dangerous course of action as security issues may arise.... perhaps if the first issue was resolved, an additional step in the upgrade process to allow the user to either re-enable, or purge sources/PPA's could be included. Any sources referencing the old release could be stepped forward, and sources using a generic release ID such as Chrome would need no modification...
Ultimately, it is obviously desirable to give the user a clean upgrade, but perhaps not at the expense of then being exposed to major security risk.
It seems that in the past it was the case that if one package source failed, then no updates would be executed by the update manager. I'm not certain if this issue has been fixed.
As regards the issue raised above, it does seem that simply disabling sources/PPA's after software is already installed is a dangerous course of action as security issues may arise.... perhaps if the first issue was resolved, an additional step in the upgrade process to allow the user to either re-enable, or purge sources/PPA's could be included. Any sources referencing the old release could be stepped forward, and sources using a generic release ID such as Chrome would need no modification...
Ultimately, it is obviously desirable to give the user a clean upgrade, but perhaps not at the expense of then being exposed to major security risk.