On Tue, Mar 24, 2009 at 11:24 AM, Martin Pitt <mp...@debian.org> wrote: > reassign 520992 postgresql-common 96 > > Chris Lawrence [2009-03-24 8:57 -0500]: >> 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)? > > Eww, thanks for pointing out. I realize now that the program > lsb_release is now actually shipped in the package lsb-release, and > not in lsb-base as in earlier times. Thus I need to update the > dependency to lsb-release. > > Sorry for too quick reaction before,
If it's any consolation... I missed it too (when running dpkg --status I saw lsb-base and just assumed lsb-release was there too). What I get for not paying close enough attention! Chris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
