Can't upgrade dapper to hardy
After running do-release-upgrade I get the following error:
Getting upgrade prerequisites failed
The system was unable to get the prerequisites for the upgrade. The
upgrade will abort now and restore the original system state.
Please report this as a bug against the 'update-manager' package and
include the files in /var/log/
Restoring original system state
Aborting
Question information
- Language:
- English Edit question
- Status:
- Expired
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
There is a
There is also a vibrant support community available at http://
Revision history for this message
|
#2 |
Uhoh, sorry, my comment has been shorten.
There is a way to upgrade which is documented there https:/
If the recommended way in the documentation doesn't work, you can apply latest updates to dapper from the old-releases archive, then point your sources.list to hardy, update and dist-upgrade.
Be very careful to what is installed/removed when doing it this way, because the release upgrader won't take care of very specific upgrade paths doing it this way.
And
There is also a vibrant support community available at http://
I'm converting this report to a question where you'll be able to get support from there.
Revision history for this message
|
#3 |
The way to upgrade documented at https:/
2011-07-26 18:23:36,519 INFO release-upgrader version '0.87.31' started
2011-07-26 18:23:36,523 DEBUG Using 'DistUpgradeVie
2011-07-26 18:23:36,584 DEBUG enable dpkg --force-overwrite
2011-07-26 18:23:36,645 DEBUG lsb-release: 'dapper'
2011-07-26 18:23:36,645 DEBUG _pythonSymlinkCheck run
2011-07-26 18:23:37,139 DEBUG checkViewDepends()
2011-07-26 18:23:37,139 DEBUG need backports
2011-07-26 18:23:37,139 DEBUG getRequiredBack
2011-07-26 18:23:37,139 DEBUG writing prereuists sources.list at: '/etc/apt/
2011-07-26 18:23:37,185 DEBUG adding '# sources.list fragment for pre-requists (mirror from sources.list + fallback)
' prerequists
2011-07-26 18:23:37,185 DEBUG adding '# this is safe to remove after the upgrade
' prerequists
2011-07-26 18:23:37,185 DEBUG adding '
' prerequists
2011-07-26 18:23:37,186 DEBUG adding 'deb http://
' prerequists
2011-07-26 18:23:37,186 DEBUG running doUpdate() (showErrors=False)
2011-07-26 18:23:39,177 ERROR IOError/SystemError in cache.update(): 'Failed to fetch http://
'. Retrying (currentRetry: 0)
2011-07-26 18:23:40,572 ERROR IOError/SystemError in cache.update(): 'Failed to fetch http://
'. Retrying (currentRetry: 1)
2011-07-26 18:23:41,818 ERROR IOError/SystemError in cache.update(): 'Failed to fetch http://
'. Retrying (currentRetry: 2)
2011-07-26 18:23:41,819 ERROR doUpdate() failed completely
2011-07-26 18:23:43,621 ERROR Can not find backport 'release-
2011-07-26 18:23:43,622 DEBUG writing prereuists sources.list at: '/etc/apt/
2011-07-26 18:23:43,663 DEBUG adding '# sources.list fragment for pre-requists (mirror from sources.list + fallback)
' prerequists
2011-07-26 18:23:43,663 DEBUG adding '# this is safe to remove after the upgrade
' prerequists
2011-07-26 18:23:43,663 DEBUG adding 'deb http://
deb http://
deb http://
deb http://
' prerequists
2011-07-26 18:23:43,664 DEBUG adding 'deb http://
' prerequists
2011-07-26 18:23:43,664 DEBUG running doUpdate() (showErrors=False)
2011-07-26 18:23:45,061 ERROR IOError/SystemError in cache.update(): 'Failed to fetch http://
'. Retrying (currentRetry: 0)
2011-07-26 18:23:46,462 ERROR IOError/SystemError in cache.update(): 'Failed to fetch http://
'. Retrying (currentRetry: 1)
2011-07-26 18:23:47,866 ERROR IOError/SystemError in cache.update(): 'Failed to fetch http://
'. Retrying (currentRetry: 2)
2011-07-26 18:23:47,866 ERROR doUpdate() failed completely
Revision history for this message
|
#4 |
The URL in the previous post's log file that got shortened and returns a 404 error is below:
I think it was moved to:
Revision history for this message
|
#5 |
Does this really mean CANONICAL has locked out every user of 6.06 LTS from upgrading to 8.04 LTS ?!?
Revision history for this message
|
#6 |
Theoretically, one could futz with local DNS server to make archive.ubuntu point instead to old-releases.
Revision history for this message
|
#7 |
Also, askubuntu is not vibrant support, it's a mass of idiotic questions that are all unrelated to this issue.
Revision history for this message
|
#8 |
I think it is the upgrade manager package that causes this error, it was fixed in more recent versions but the most recent version available for dapper 6.06 LTS was not fixed.
Revision history for this message
|
#9 |
I am still suffering form this bug. I cannot upgrade my dist via upgrade manager. the required packages have moved. I try to update my package list every once in a while to see if anyone has been working on this.. but so far nothing.
Next I tried scanning through the script to see if the repository was hard-linked in there, but I'm not really too pro at debugging python... i couldn't find it. While doing that i tried to see if the script took any arguments... maybe perhaps an alternate repository url argument... but again, I'm not pro enough yet.
doing some local DNS gymnastics just to make a dummy prerequisite list seems a little bit over the top for this problem... I'm sure there's an easier fix...
I'm going to keep scanning the script.... hopefully I'll find something.
Someone who developed this should help us out.. please.
Revision history for this message
|
#10 |
Jonathan, you might try checking post 54-56 of following thread:
https:/
It is for different versions but I think the same problem. I have not tried what they mention but it looks like they modifed the upgrade script to pause during the upgrade so you can go edit the files to contain the correct information before resuming.
Revision history for this message
|
#11 |
Thanks for that john! #56 for the win. That guy says he did it for dapper to hardy.
https:/
Revision history for this message
|
#12 |
Your welcome, hope it works for you. I plan to soon give it a try as well.
Revision history for this message
|
#13 |
alright! I just tried that fix and I am happy to confirm, that this BUG IS NO MORE! (at least for me)
Follow this link:
https:/
#54-56
Here's a few things to keep in mind when updating, using this fix:
1. The do-release-upgrade script creates a new /tmp/tmpXXXXX/ directory every time you run the script. If you've run the script before, don't edit files in an old tmp dir. I did that the first time XP.
2. Don't worry about prerequists-
3. The files that you need to edit are /tmp/tmpxxxxxx/
That's it. good luck everyone!
Revision history for this message
|
#14 |
sorry typo: second file is /etc/apt/
Revision history for this message
|
#15 |
This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.