Matthew, did you ever get around to work on this? These (post zesty archive removal / migration) days, no hour passes without someone joining #ubuntu seeking help with 'broken repositories', for example:
--- begin quote --- <user1> this just started happening, seemingly without reason: E: The repository 'http://security.ubuntu.com/ubuntu zesty-security Release' does no longer have a Release file. <user1> N: Updating from such a repository can't be done securely, and is therefore disabled by default. <user1> N: See apt-secure(8) manpage for repository creation and user configuration details. <user1> same issue with other repos <user1> are ubuntu repo servers experiencing issues that somehow affect mirrors? --- end quote --- --- begin quote --- <user2> hey, did anyone notice the Release files are missing from zesty? <user2> E: The repository 'http://de.archive.ubuntu.com/ubuntu zesty-updates Release' does no longer have a Release file. <user2> E: The repository 'http://de.archive.ubuntu.com/ubuntu zesty-updates Release' does no longer have a Release file. --- end quote --- This affects also people knowledgeable enough to install Ubuntu server and to work with virtualization, so not just the elderly non-tech person depicted in the original description, but the average and possibly experienced user, too. And only those who can make their way to IRC actually have a chance to learn how to recover from it. With the level of maturity and usability Ubuntu has reached nowadays, I believe that providing - a (possibly repeatable / snoozable) warning that EOL is approaching and - an information on how to easily recover from EOL state (or, possibly better, instrumentation which automates the procedure) are duly needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/319146 Title: When a release reaches End-of-Life, update manager should show EoL status and provide a link with working procedures and more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/319146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
