[Dbconfig-common-devel] updating/installing when user and grants already exist

[Tobias Grimm]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig369718DD2343FDB15FA4D37F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hello!

When updating from an earlier version, which not used dbc, I run into
problems. dbc asks for the db user password and changes it in the
config. But it doesn't change it in the database.

Any ideas?

I think, the problem is, that dbc doesn't touch the user, if it already
exists. Should dbc be able to change a user or should I purge it (or
revoke the grants) before upgrading to the new package version with dbc?

The same problem appears, when you install a dbc-enabled package, then
purge it without dropping the database and then install it again. In
this case the user password isn't changed in the either, because the
grants already exist. But the password is changed in the config!

bye,

Tobias

--------------enig369718DD2343FDB15FA4D37F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQEVAwUBQoVWNNuQ2Pwwa2eDAQK6dQf/QVrqT9TvE14t3dGql/zMCrDAZH0Huo1+
OEuKUv0cfBPC7pkVjKv2AJm5ZLxAUtZmx32SMJktNkdTggUBjQlmK2PPovZWaEVK
fzOkR/m9H5zjORAdY+iGU+0HkhHpOoVeq+ZLx1MYo61ONkLoNXUxiJHpYn8u3aml
JVOJWzBh1Wkea2kXsjsnIM7FBeCx2lKzB8NlKZF+vr7ShjUWLQd9zk1wLIcrokFy
E9ofciV5rV9duCMH8V6axxg979dJBhSnsCA/5Jwlcxmaks9gfDJg4W8gBAjKxtWV
1RuzZQ9SDqL4I9S1D9GG9i/tcyUYwelH24orWnLA3Xu7Fs5XHq0sQQ==
=5p/g
-----END PGP SIGNATURE-----

--------------enig369718DD2343FDB15FA4D37F--