bacula-director-pgsql does not install cleanly with db-config

Bug #563084 reported by Jakub Witkowski
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bacula (Ubuntu)
Invalid
Medium
Unassigned
Lucid
Invalid
Medium
Unassigned
dbconfig-common (Debian)
Fix Released
Unknown
dbconfig-common (Ubuntu)
Fix Released
High
Thierry Carrez
Lucid
Fix Released
High
Thierry Carrez

Bug Description

Binary package hint: bacula-director-pgsql

The package postinst script (through db-config) does not set template database properly and thus the database creation fails:

Creating config file /etc/dbconfig-common/bacula-director-pgsql.conf with new version
creating postgres user bacula: success.
verifying creation of user: success.
creating database bacula: failed.
error encountered creating database:
ERROR: new encoding (SQL_ASCII) is incompatible with the encoding of the template database (UTF8) HINT: Use the same encoding as in the template database, or use template0 as template.
dbconfig-common: bacula-director-pgsql configure: ignoring errors from here forwards

The bacula database should be set to SQL_ASCII, as evidenced here: http://www.bacula.org/5.0.x-manuals/en/main/main/Installing_Configuring_Post.html#SECTION004220000000000000000

Steps to repeat:

1. Install postrgesql server
2. Install bacula-director-pgsql
3. Select configure the database via dbconfig

This is Ubuntu 10.04 (up to date as of 14.04.2010)
Package bacula-director-pgsql 5.0.1-1ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: bacula-director-pgsql 5.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic x86_64
NonfreeKernelModules: openafs nvidia
Architecture: amd64
Date: Wed Apr 14 16:30:52 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100316)
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: bacula

Revision history for this message
Jakub Witkowski (jakub.witkowski) wrote :
Scott Moser (smoser)
Changed in bacula (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Scott Moser (smoser) wrote :
Changed in dbconfig-common (Ubuntu):
status: New → Confirmed
Revision history for this message
Scott Moser (smoser) wrote :

Marking this as 'High' importance as anything that uses dbconfig-common and pgsql is broken

Changed in dbconfig-common (Ubuntu):
importance: Undecided → High
Changed in dbconfig-common (Debian):
status: Unknown → Fix Released
Revision history for this message
Thierry Carrez (ttx) wrote :

IIUC it only affects dbc_pgsql_createdb_encoding, but should still be fixed.

Changed in bacula (Ubuntu Lucid):
status: Confirmed → Invalid
Revision history for this message
Thierry Carrez (ttx) wrote :

Moving to 1.8.46 is a little too much, as 1.8.45 changes some behavior, see posted 1.8.44->1.8.46 debdiff for reference. I'll cherrypick the fix and propose that instead.

Changed in dbconfig-common (Ubuntu Lucid):
assignee: nobody → Thierry Carrez (ttx)
status: Confirmed → In Progress
Revision history for this message
Thierry Carrez (ttx) wrote :
Changed in dbconfig-common (Ubuntu Lucid):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dbconfig-common - 1.8.44ubuntu1

---------------
dbconfig-common (1.8.44ubuntu1) lucid; urgency=low

  * Fix pgsql createdb code to use template0 when encoding is specified,
    patch from Sean Finney cherrypicked from debian's 1.8.46 (LP: #563084)
 -- Thierry Carrez <email address hidden> Fri, 16 Apr 2010 15:37:49 +0200

Changed in dbconfig-common (Ubuntu Lucid):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.