For each release, always create all dists in repo, even when empty

[Pander]

People can upgrade by altering their /etc/apt/sources.list file. They typically rename e.g. quantal to raring and do an apt-get dist-upgrade.

With the release of 13.04, not all dists have been created in the repo. See http://archive.canonical.com/ubuntu/dists/

which has:
[DIR] quantal-backports/ 26-Apr-2012 18:44 -
[DIR] quantal-proposed/ 26-Apr-2012 18:44 -
[DIR] quantal-security/ 26-Apr-2012 18:44 -
[DIR] quantal-updates/ 26-Apr-2012 18:44 -
[DIR] quantal/ 26-Apr-2012 18:44 -
but for raring ans saucy it has:
[DIR] raring-proposed/ 01-Feb-2013 20:53 -
[DIR] raring/ 23-Oct-2012 11:23 -
[DIR] saucy-proposed/ 26-Apr-2013 09:35 -
[DIR] saucy/ 26-Apr-2013 11:35 -

This means that if people use raring, they have to comment out updates, security and backports in sources.list and monitor manually when these are available and enable these by uncommenting. Otherwise apt-get upgrade is complaining about it.

This is a far from ideal situation since these mechanism are there to automate upgrades flawlessly. Please fix this by creating (even if empty) dists for updates, security and backports for any Ubuntu release before it is official. (So please do that for raring and already for saucy). Errors from apt-get update are:

W: Failed to fetch http://archive.canonical.com/ubuntu/dists/raring-updates/partner/binary-amd64/Packages 404 Not Found [IP: 91.189.92.191 80]

W: Failed to fetch http://archive.canonical.com/ubuntu/dists/raring-updates/partner/binary-i386/Packages 404 Not Found [IP: 91.189.92.191 80]

E: Some index files failed to download. They have been ignored, or old ones used instead.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Pander (pander)]

For those interested personally: https://github.com/PanderMusubi/apt-sources

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1173570/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]