Sorry, if I was the one Generating the Error Messages to the Developer's, went into my Sources List and Found Referrences Still Referring to Raring! I changed all to Saucy, now I'm Fully In for good.
Everything is working well here after putting in just those three commands. It can also be done like this:
sudo sed -i 's/raring/saucy/g' /etc/apt/sources.list
sudo apt-get update
sudo apt-get upgrade
Please note that I do not advise (nor did I advise) that this proceedure be executed on a production machine. Unless you have an extra hdd or other machines or are an experienced beta tester then stick with the safe and stable route. I have 8 towers and 3 laptops all commited to testing. It is conventional wisdom that system will break in these early stages - so unless one has an extra surplus machine then early beta testing should be deferred.
As competition would have it , Windows 8 has far exceeded Ubutnu on various form factors and so I am looking forward to this release as being the new 'setting of the bar' which will bring ubuntu up to speed. Just in my own opinion but I see raring as a sandbox/blackboarding exercise for a much more workable Saucy Salamander :)
For me a sudo gedit /etc/apt/sources.list worked better than your 3 commands. I then changed all references of raring to saucy. A lsb_release -a command now shows me at 13.10 Development Branch.
I'm really pumped for this Saucy cycle. It seems to be pulling updates.
For any one who are still having problems with software-properties-gtk crashing
you can check this to see if the release got updated. sometimes it doesn't ;-)
Then edit the file that opens so that it looks like thisCode:
gksudo gedit /etc/lsb-release
Remember to enter which version of ubuntu you are using.Code:
Then go back to the terminal after you have saved the lsb-release file and you should be able to add-apt-repository
taken from http://askubuntu.com/questions/49040/apt-could-not-find-a-distribution-template-error
I don't think it's wise to do this until you know that the new toolchain has been uploaded :)
Within a few weeks, wouldn't i be able to do the upgrade through the software updater? I remember someone had posted a way of putting in like 2 terminal commands that would have the software updater bring up the option of upgrade (which i guess it normally only does when a newer version goes final)...i have my software updater set to notify of any new versions...
I was glad that at least my software updater reverted back to raring (when saucy didn't come in through the terminal) when i hit "edit" and logged into the updater cause all the check boxes had blanke dout but they come back to normal with the proper settings once i logged in....
This is why we need that new simpler method the developers are working on which will enable you to simply point to the next version when it's ready for updates...that would make life simpler with this change over business...
If anyone wanted to know how to upgrade they could have just looked at the sticky.