It's impossible to reconstruct this bug because it's not a bug in update-manager but rather in lsb_release.
Have a close look at the traceback, which clearly shows that lsb_release caused an error and prints out the lsb_release traceback (which obviously is also a Python program). So putting it all together we can safely close this bug report or reassign it to lsb_release, even though I guess this bug has already been fixed there. Could someone else do that because I do not have that much time for bug management right now? Regards, Stephan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
