[Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

[Paul Gevers]

Control: clone -1 -2
Control: reassign -2 dbconfig-common
Control: retitle -2 dbc: db-dump must use root credentials when needed

Hi all,

I think I found the issue. Since commit 95571e6¹ the postinst script of
dbconfig properly executes install code with user privileges as it has
always said it would. Therefore, before dbconfig-common 1.8.50, the
install code would be run with the administrator credentials. Indeed,
this results in the behavior as now observed.

Therefore, what I think what needs to be done is the following:
1) dbconfig-common needs to be fixed to cope with procedures not owned
by the user during database dumping
2) tango-db needs to change ownership of the procedures using dbadmin
privileges. As the order of execution of user sql vs dbadmin sql vs
scripts is undetermined, this probably means that for one version
tango-db needs to ship a script to do the actual actions it would
normally put in /usr/share/dbconfig-common/data/tango-db/upgrade/ (after
it first drops the procedures).

Of to bed now.

Paul

¹
https://anonscm.debian.org/cgit/collab-maint/dbconfig-common.git/commit/?id=95571e657e1d57e6b81a6a352b9cf49bcb5469d1

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20170104/9bdd848b/attachment.sig>