Bug#848137: RE:Bug#848137: Info received (problem with the upgrade of tango-db)

Paul Gevers elbrus at debian.org
Tue Jan 3 21:31:24 UTC 2017


Hmmm,

On 03-01-17 22:07, Paul Gevers wrote:
> On 03-01-17 21:21, PICCA Frederic-Emmanuel wrote:
>> 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 ?
> 
> Let me check the (huge) delta between jessie and stretch (hopefully
> tomorrow). I made major improvements in the code, but I don't
> specifically remember anything related to this issue. Furthermore, I
> don't rule out that this is indeed MySQL/MariaDB related. We/you could
> also ask the maintainers list of those packages if the current behavior
> rings a bell. Additionally, trying to do the tests as you did so far but
> sticking to MySQL instead of moving over to MariaDB would be an
> interesting and insightful exercise.

I am suspecting that this commit may be related to the current behavior:
https://anonscm.debian.org/cgit/collab-maint/dbconfig-common.git/commit/?id=acdb99d61abfff54630c4cfba6e4452357a83fb9

I believe I implemented there that the drop of the database is performed
with the user privileges instead of the dbadmin privileges because I
believed one should always have the rights to drop the db. Apparently I
was wrong. We may need to clone or reassign this bug to dbconfig, but
I'm not sure yet if there aren't more things, or if tango-db should work
around the issue (which may be created by buggy dbconfig-common behavior
of the past).

Out of time now.

Paul

-------------- 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/debian-science-maintainers/attachments/20170103/511b11de/attachment.sig>


More information about the debian-science-maintainers mailing list