I spent quite some time debugging this yesterday adding extra information on the logs and I finally found that it's a transient error due to the state of the remote mirror. Using archive.ubuntu.com makes no difference (I guess because it's not the mirror master).
Thus, after trying many times, do-release-upgrade eventually accepted all packages as trusted. Tried a couple of times more and it worked fine each time. A few minutes later it failed again. All this without any changes in the code, so the problem is that something is happening in the remote end that lucid doesn't like. I also found that the workaround didn't work (I'm not sure why) so this is what I did: 1. run do-release-upgrade and wait until it fails 2. cd $(ls -trd /tmp/tmp* | tail -1) 3. edit DistUpgradeCache.py and find the comment "check if the user overwrote the unauthenticated warning" 4. add a new line below with "return True" that will avoid aborting and save the file 5. run ./precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513232 Title: do-release-upgrade no longer works from lucid to precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1513232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
