| 2007-07-20 20:33:08 |
Will Newton |
bug |
|
|
added bug |
| 2007-07-27 18:06:24 |
Will Newton |
bug |
|
|
assigned to update-manager (Ubuntu) |
| 2007-07-29 16:28:05 |
Wousser |
marked as duplicate |
|
103911 |
|
| 2007-08-02 12:46:43 |
Juan Pablo Salazar BertÃn |
removed duplicate marker |
103911 |
|
|
| 2007-08-02 18:23:19 |
Bruce Cowan |
update-manager: status |
New |
Confirmed |
|
| 2007-08-02 18:23:19 |
Bruce Cowan |
update-manager: statusexplanation |
|
Indeed it isn't, and I can confirm this issue. |
|
| 2007-08-08 08:44:22 |
Michael Vogt |
update-manager: importance |
Undecided |
High |
|
| 2007-08-08 08:44:22 |
Michael Vogt |
update-manager: assignee |
|
mvo |
|
| 2007-08-08 08:44:22 |
Michael Vogt |
update-manager: statusexplanation |
Indeed it isn't, and I can confirm this issue. |
|
|
| 2007-08-08 10:32:21 |
Michael Vogt |
bug |
|
|
added attachment 'u-m.diff' (Patch to fix the issue. Can you please try the attached patch?) |
| 2007-08-08 10:33:43 |
Michael Vogt |
update-manager: status |
Confirmed |
Fix Committed |
|
| 2007-08-08 10:33:47 |
Michael Vogt |
update-manager: status |
New |
Fix Committed |
|
| 2007-08-08 10:33:47 |
Michael Vogt |
update-manager: statusexplanation |
|
|
|
| 2007-08-11 17:07:03 |
Bruce Cowan |
update-manager: status |
Fix Committed |
Fix Released |
|
| 2007-08-11 17:07:12 |
Bruce Cowan |
update-manager: status |
Fix Released |
Fix Committed |
|
| 2007-08-20 16:30:10 |
Michael Vogt |
update-manager: status |
Fix Committed |
Fix Released |
|
| 2007-09-06 15:05:53 |
Bruce Cowan |
update-manager: status |
Fix Released |
Fix Committed |
|
| 2007-09-10 10:15:25 |
Michael Vogt |
bug |
|
|
added attachment 'update-manager_0.59.24.debdiff' (Debdiff that fixes the issue) |
| 2007-09-10 10:16:06 |
Michael Vogt |
update-manager: importance |
Undecided |
Medium |
|
| 2007-09-10 10:16:06 |
Michael Vogt |
update-manager: assignee |
|
mvo |
|
| 2007-09-10 10:16:06 |
Michael Vogt |
update-manager: status |
New |
In Progress |
|
| 2007-09-10 10:17:19 |
Michael Vogt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2007-09-12 22:33:47 |
Michael Heimann |
bug |
|
|
added attachment 'meta-release' (working meta-release file) |
| 2007-09-14 14:13:52 |
Michael Vogt |
update-manager: status |
Fix Committed |
Fix Released |
|
| 2007-09-14 14:14:38 |
Michael Vogt |
update-manager: status |
Fix Committed |
Fix Released |
|
| 2007-09-14 14:40:56 |
Martin Pitt |
update-manager: status |
In Progress |
Fix Committed |
|
| 2007-09-14 14:41:16 |
Martin Pitt |
description |
The symptom is that if I do gksudo "update-manager -d" I get no option to upgrade and this error:
current dist not found in meta-release file
Looking at the code in:
/usr/lib/python2.5/site-packages/UpdateManager/Core/MetaRelease.py
It seems I had a zero sized METARELEASE_FILE. This was being created by the __init__ method of MetaReleaseCore:
try:
open(self.METARELEASE_FILE,"a")
except IOError, e:
path = os.path.expanduser("~/.update-manager-core/")
if not os.path.exists(path):
os.mkdir(path)
self.METARELEASE_FILE = os.path.join(path,"meta-release")
Then the download() method checks the mtime of METARELEASE_FILE in order to add an If-Modified-Since header to the http request. The mtime is very recent because we just touched it in __init__. Because of this urllib throws an exception with HTTP 304 Not Modified.
The exception handler then sees the empty METARELEASE_FILE:
except urllib2.URLError:
if os.path.exists(self.METARELEASE_FILE):
self.metarelease_information=open(self.METARELEASE_FILE,"r")
And sets metarelease_information to the newly opened empty file. Later on a parse is attempted on this file which results in no meta-release information matching the current distro.
Fix/workaround:
Taking the last-modified check out works, but probably the best thing to do is to check for a zero sized file at the same time as reading the mtime. |
The symptom is that if I do gksudo "update-manager -d" I get no option to upgrade and this error:
current dist not found in meta-release file
Looking at the code in:
/usr/lib/python2.5/site-packages/UpdateManager/Core/MetaRelease.py
It seems I had a zero sized METARELEASE_FILE. This was being created by the __init__ method of MetaReleaseCore:
try:
open(self.METARELEASE_FILE,"a")
except IOError, e:
path = os.path.expanduser("~/.update-manager-core/")
if not os.path.exists(path):
os.mkdir(path)
self.METARELEASE_FILE = os.path.join(path,"meta-release")
Then the download() method checks the mtime of METARELEASE_FILE in order to add an If-Modified-Since header to the http request. The mtime is very recent because we just touched it in __init__. Because of this urllib throws an exception with HTTP 304 Not Modified.
The exception handler then sees the empty METARELEASE_FILE:
except urllib2.URLError:
if os.path.exists(self.METARELEASE_FILE):
self.metarelease_information=open(self.METARELEASE_FILE,"r")
And sets metarelease_information to the newly opened empty file. Later on a parse is attempted on this file which results in no meta-release information matching the current distro.
Fix/workaround:
Taking the last-modified check out works, but probably the best thing to do is to check for a zero sized file at the same time as reading the mtime. |
|
| 2007-09-14 18:22:38 |
Michael Hofmann |
bug |
|
|
added attachment 'updatemanager-os.patch' (updatemanager-os.patch) |
| 2007-09-16 09:47:33 |
Martin Pitt |
update-manager: status |
Fix Committed |
In Progress |
|
| 2007-09-24 19:13:46 |
William F Pearson |
bug |
|
|
added attachment 'meta-release.txt' (save in /var/lib/update-manager/meta-release) |
| 2007-09-26 16:15:34 |
Martin Pitt |
update-manager: status |
In Progress |
Fix Released |
|
| 2010-02-22 00:31:39 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/update-manager |
|
| 2010-02-22 00:38:07 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/feisty-proposed/update-manager |
|
