Python traceback was presented upon upgrade from dapper to edgy

Binary package hint: update-manager

I'm not sure if the upgrade actually finished before it gave me this error, or not. I was presented with a nice dialog box, though, that handed me a Python stack trace and asked me to report a bug (note: it didn't tell me where to report the bug at or which package to report it against, which would be handy for some folks). It asked me to attach my main.log and apt.log files from /var/log/dist-upgrade/.

It looks like the problem is a simple mis-spelling of the word "logging" as "loggging":
------------------------------------------------------------------------
Traceback (most recent call last):

  File "/tmp/tmpglmaBv/edgy", line 40, in ?
    app.run()

  File "/tmp/tmpglmaBv/DistUpgradeControler.py", line 755, in run
    self.edgyUpgrade()

  File "/tmp/tmpglmaBv/DistUpgradeControler.py", line 745, in edgyUpgrade
    self.doPostUpgrade()

  File "/tmp/tmpglmaBv/DistUpgradeControler.py", line 545, in doPostUpgrade
    if not self.cache._tryMarkObsoleteForRemoval(pkgname, remove_candidates, self.foreign_pkgs):

  File "/tmp/tmpglmaBv/DistUpgradeCache.py", line 352, in _tryMarkObsoleteForRemoval
    loggging.warning("_tryMarkObsoleteForRemoval failed for '%s' (%s)" % (pkgname,e))

NameError: global name 'loggging' is not defined
------------------------------------------------------------------------

(Very sorry if this is a duplicate. I looked around a little and was surprised to not find a bug report, already, for this problem.)