Bug#289838: Creating databases for the bacula-director

[Jos Luis Talln]

Joerg Friedrich wrote:
Hi,
just a hint, maybe I have the time to look deeper into it at the
weekend.
Don't reinvent the wheel when creating databases in postinst, resp.
removing them on purge. Use the wwwconfig-common framework.
 

No, that is not an option right now:
- wwwconfig-common is *deprecated* for DB-related config
- we are too close to a release
The package name might be misleading the package supports additionally
to manipulating the apache and php config also creating and
removing of database, user... for mysql and postgres.
 

Yes, I know. That is why is proposed a migration to *dbconfig-common* 
[which was designed precisely for this purpose] long ago.

These packages have rdepends on wwwconfig-common. most of them just use
it for configuring apache and php, but some of them to create databases
and db users. Esp. horde2 is a very good one.
 

Well, those packages will start receiving RC bugs to get them migrated 
to wwwconfig-common + dbconfig-common (or just one of them, as 
appropiate), as soon as dbconfig-common has been completely tested 
(specially by means of a series of experimental bacula-director 
package releases) and Sarge has been released.

Sorry if i sounded too harsh, but there is no way that i can get 
everything migrated with so little time. And then, wwwconfig-common is 
quite a mess to be used in Bacula's postinst scripts -- dbconfig-common 
is the way to go.
Anyways, your attention and suggestion is very much appreciated. Please 
keep the feedback coming.

Best,
   J.L.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#289838: postinst script unusable due to serious errors

[Jos Luis Talln]

Rafal Krzewski wrote:
Package: bacula-director-pgsql
Version: 1.36.1-1
Severity: critical
1) the script attempts to use $DB_ADMIN and $dbadmin variables that 
are never set. Would expect them to be set from conf variable 
bacula-director-pgsql/pgsql_root_username but the script does not do 
that.

2) the script uses incorrect su command syntax. It sets the following 
variable:
PGSQLCMD=su -s /bin/sh $dbadmin -c /usr/bin/psql
And then attempts to execute the command appeding different suffixes 
to the variable value. Su expects the username as the last argument. IE
su -c psql postgres -l does not work, but su -c psql -l postgres 
works. Because of that all su invocations PGSQLCMD invocations in the 
script need to be changed.

There may be more problems, but the above are definite showstoppers.
I am no PostgreSQL admin. The tag HELP is set since several weeks ago, 
and nobody answered.
The PostgreSQL is completely unsupported as of now.
Please feel free to send me patches providing the functionality you need 
and i'll be more than happy to integrate them.

Best,
   J.L.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]