Package: keystone Version: 2012.1.1-13 Severity: minor Dear Maintainer, *** Please consider answering these questions, where appropriate ***
* What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** After initial configuration Keystone fails to connect to Postgres. Connection type should be changed from "pgsql" to "postgresql" or starting the service will fail with message from sqlalchemy: "Could not determine dialect for 'pgsql'." -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages keystone depends on: ii adduser 3.113+nmu3 ii dbconfig-common 1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.49 ii lsb-base 4.1+Debian8 ii python 2.7.3-4 ii python-keystone 2012.1.1-13 ii python-keystoneclient 2012.1-3 keystone recommends no packages. keystone suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org