If lsb-release and postgresql-common were upgraded during the same dpkg/apt run, it's possible lsb-release hadn't been configured yet (thus the Python module lsb_release.py wasn't in the search path) when postgresql-common was configured. Perhaps changing the dependency on lsb-release to >= 3.2-22 will fix the problem (e.g. force lsb-release to be configured before postgresql-common)?
I assume lsb_release 3.2-22 works OK in the general case (in part because I haven't seen any bug reports to this effect, and in part because it works on my system). Chris -- Chris Lawrence <lawre...@debian.org> - http://blog.lordsutch.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
