not possible to upgrade to raring

Well, it looks like everything in __init__ in DistUpgradeFetcherCore is missing:

(Pdb) dir(fetcher)
['DEBUG', 'DEFAULT_COMPONENT', 'DEFAULT_MIRROR', '__class__', '__delattr__', '__dict__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__gt__', '__hash__', '__init__', '__le__', '__lt__', '__module__', '__ne__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', '_debug', '_expandUri', 'authenticate', 'cleanup', 'error', 'extractDistUpgrader', 'fetchDistUpgrader', 'gpgauthenticate', 'mirror_from_sources_list', 'run', 'runDistUpgrader', 'showReleaseNotes', 'verifyDistUprader']

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

Looks like the command line version does't instantiate the DistUpgradeFetcherCore class. The fix should be easy; I'll SRU a fix into quantal-proposed.

From bug 1077938, I merged lp:~toabctl/ubuntu-release-upgrader/fix-release-upgrade which fixes this into trunk. But it still needs an SRU. I'll leave that for Barry, since he's assigned.

Actually, the SRU is in progress. It's sitting in the unapproved queue waiting for approval.

https://launchpad.net/ubuntu/quantal/+queue?queue_state=1&queue_text=ubuntu-release-upgrader

Uploaded to raring and pushed update to lp:ubuntu-release-upgrader

Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:0.190.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

This bug was fixed in the package ubuntu-release-upgrader - 1:0.192

---------------
ubuntu-release-upgrader (1:0.192) raring; urgency=low

  * do-release-upgrade:
    - Fix crasher when not using gtk (LP: #1076186)
 -- Michael Terry <email address hidden> Tue, 13 Nov 2012 10:18:47 -0500

I installed ubuntu-release-upgrade-core version 1:0.190.4 from quantal-proposed and then was able to start the upgrade to Raring. Marking as verification-done.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package ubuntu-release-upgrader - 1:0.190.4

---------------
ubuntu-release-upgrader (1:0.190.4) quantal-proposed; urgency=low

  * Fix command line invocation of "./do-release-upgrade -d"
    LP: #1076186
  * debian/rules: setup.py is only compatible with Python 3, but the
    dh_auto_* commands don't know how to invoke Python 3 yet. So
    disable the up-calls in override_dh_auto_{build,install} since
    they aren't needed, and provide the explicit call for
    override_dh_auto_clean.
 -- Barry Warsaw <email address hidden> Thu, 08 Nov 2012 15:13:39 -0500

I'm still getting this on a fully updated 12.10 server x64 install. :(

# do-release-upgrade
Checking for a new Ubuntu release
Traceback (most recent call last):
  File "/usr/bin/do-release-upgrade", line 145, in <module>
    fetcher.run_options += ["--mode=%s" % options.mode,
AttributeError: type object 'DistUpgradeFetcherCore' has no attribute 'run_options'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 137, in apport_excepthook
    os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
OSError: [Errno 2] No such file or directory: '/var/crash/_usr_bin_do-release-upgrade.0.crash'

Original exception was:
Traceback (most recent call last):
  File "/usr/bin/do-release-upgrade", line 145, in <module>
    fetcher.run_options += ["--mode=%s" % options.mode,
AttributeError: type object 'DistUpgradeFetcherCore' has no attribute 'run_options'

What is the output of the following command?

apt-cache policy python3-distupgrade

Looks like it was user error. I didn't have the quantal-updates repo in my /etc/apt/sources.list. For anyone else, I documented it, here:

http://www.prestonlee.com/2013/04/26/ubuntu-12-10-to-13-04-server-upgrade-error/