Comment 4 for bug 1310891

Revision history for this message
uwe (maabdulhaq) wrote : Re: attempting to trigger upgrade from 13.04 (raring) to 13.10 (saucy) claims that No new release found

I did;

tried this :

# DEBUG_UPDATE_MANAGER=1 /usr/bin/do-release-upgrade
Checking for a new Ubuntu release
MetaRelease.__init__() useDevel=False useProposed=False
/etc/update-manager/meta-release: -development
/etc/update-manager/meta-release: -proposed
reading file '/var/lib/update-manager/meta-release'
have self.metarelease_information
current dist name: 'raring'
current dist not found in meta-release file

No new release found
root@taz:~# cat /var/lib/update-manager/meta-release
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "">
<html xml:lang="ar" lang="ar" dir="rtl" xmlns="">
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
  <meta name="robots" content="noindex,nofollow"/>

removed /var/lib/update-manager/meta-release ; now things seem to go fine. yet I don't know why it is not attempting to remove old/corrupted/wrong files or refresh their content ...