I looked into ths today and it turns out the bug is really that pyhton-apt in hardy-updates calls apt_pkg.init() at the wrong point. So both a new python-apt and a rebuild of update-manager will be required.
I looked into ths today and it turns out the bug is really that pyhton-apt in hardy-updates calls apt_pkg.init() at the wrong point. So both a new python-apt and a rebuild of update-manager will be required.