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,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Attachment: signature.asc
Description: Digital signature

Reply via email to