Bug#848137: RE:Bug#848137: Info received (problem with the upgrade of tango-db)
PICCA Frederic-Emmanuel
frederic-emmanuel.picca at synchrotron-soleil.fr
Tue Jan 3 20:21:38 UTC 2017
> I am not sure that I follow what you are doing, but if you need the code
> to be run with the dbadmin privileges, you should put the code in:
> /usr/share/dbconfig-common/data/PACKAGE/upgrade-dbadmin/DBTYPE/VERSION
> instead of in:
> /usr/share/dbconfig-common/data/PACKAGE/upgrade/DBTYPE/VERSION
Hello Paul
I just try to use dbconfig-common like I did before,
(create the tango database, populate it with a few values and create some procedures.)
What is strange to me is that with dbconfig-common (jessie version), I end up with procedure owned by
root @ localhost
but when I use the dbconfig-common of stretch, the procedure are owned by tango @ localhost 5which is right)
I always used the non dbadmin script in order to configure my database.
This is why I do not understand why the mysqldump does not work anymore.
Does the dump changed between the jessie and strecth dbconfig-common ?
By change I mean.
In jessie it is run as root, but on stretch it is run as tango ?
Cheers
Fred
More information about the debian-science-maintainers
mailing list