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

2017-01-17 Thread PICCA Frederic-Emmanuel
> Ehm, yes. :) so I just tested an upgrade from jessie to sid of tango-db and it works :))) Now I have only one concern about the dump. Since we had a failure with the dump when it ran as user, we discovered that our procedures where wrong and necessitate the dbadmin grants in order to works.

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

2017-01-16 Thread Paul Gevers
Hi Frederic-Emmanuel, On 01/16/17 18:10, PICCA Frederic-Emmanuel wrote: >> Officially, no, because the documentation says: "If files exist in both >> data and scripts, they will both be executed in an unspecified order." >> However, the current behavior of dbconfig-common is to first run the >>

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

2017-01-16 Thread PICCA Frederic-Emmanuel
Hello Paul > Officially, no, because the documentation says: "If files exist in both > data and scripts, they will both be executed in an unspecified order." > However, the current behavior of dbconfig-common is to first run the > script and then run the admin code and then run the user code. So

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

2017-01-15 Thread Paul Gevers
Hi Picca, On 01/14/17 11:12, PICCA Frederic-Emmanuel wrote: > Hello Paul > >> I really hope I can upload this weekend. I have code that I believe does >> what I want. I am in the process of testing it. > > thanks a lot. I'll upload in the next hour. >> What I meant, >> instead of the mysql

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

2017-01-14 Thread PICCA Frederic-Emmanuel
Hello Paul > I really hope I can upload this weekend. I have code that I believe does > what I want. I am in the process of testing it. thanks a lot. > [...] > What I meant, > instead of the mysql code that runs as user, run a script for the > upgrade (they are run with database

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

2017-01-13 Thread PICCA Frederic-Emmanuel
Hello Paul, > Once I fixed 850190, Do you think that you will fix this bug before next week in order to let me enought time to fix tango and upload it. > I believe that ought to work, although that is > still a hack. I was thinking of doing the "DROP PROCEDURE IF EXISTS *" > calls with the

Bug#848137: Fwd: Re: Bug#848137: problem with the upgrade of tango-db

2017-01-09 Thread Andreas Beckmann
Forwarded Message Subject: Re: Bug#848137: problem with the upgrade of tango-db Date: Mon, 9 Jan 2017 10:00:59 +0100 From: Andreas Beckmann <a...@debian.org> To: Paul Gevers <elb...@debian.org> On 2017-01-08 22:29, Paul Gevers wrote: > It would still be

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

2017-01-08 Thread Paul Gevers
Hi Frederic, On 05-01-17 18:21, PICCA Frederic-Emmanuel wrote: > It is true that for now my package works only if the database name is tango. > > this is a limitation but I do not want to mix this into this bug report. Ack. > so can you help me write the right snipser at the right place in the

Bug#848137: problem with the upgrade of tango-db

2017-01-08 Thread Paul Gevers
Hi Andreas, On 05-01-17 13:49, Andreas Beckmann wrote: > On 2017-01-04 21:55, Paul Gevers wrote: >> Hi Frederic-Emmanuel, Andreas, >> >> @Andreas, am I correct in the assumption that jessie to stretch with >> tango-db was fine until MariaDB became the default? Or was this >> migration with

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

2017-01-05 Thread PICCA Frederic-Emmanuel
Hello, I discuss with the tango-db upstream and he found that this one line fixed the problem, befrore doing the tango-db upgrade UPDATE mysql.proc SET Definer='tango@localhost' where Db='tango'; Ideally it should be something like UPDATE mysql.proc SET Definer='xxx' where Db='yyy'; where

Bug#848137: problem with the upgrade of tango-db

2017-01-05 Thread Andreas Beckmann
On 2017-01-04 21:55, Paul Gevers wrote: > Hi Frederic-Emmanuel, Andreas, > > @Andreas, am I correct in the assumption that jessie to stretch with > tango-db was fine until MariaDB became the default? Or was this > migration with tango-db just never tested before? Have you seen other >

Processed: Re: Bug#848137: problem with the upgrade of tango-db

2017-01-04 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #848137 [tango-db] tango-db: fails to upgrade from 'jessie': mysqldump: tango has insufficent privileges to SHOW CREATE PROCEDURE `class_att_prop`! Bug 848137 cloned as bug 850190 > reassign -2 dbconfig-common Bug #850190 [tango-db] tango-db: fails

Bug#848137: problem with the upgrade of tango-db

2017-01-04 Thread 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

Bug#848137: problem with the upgrade of tango-db

2017-01-04 Thread Paul Gevers
Hi Frederic-Emmanuel, Andreas, @Andreas, am I correct in the assumption that jessie to stretch with tango-db was fine until MariaDB became the default? Or was this migration with tango-db just never tested before? Have you seen other dbconfig-common dependent packages fail since MariaDB became

Bug#848137: problem with the upgrade of tango-db

2017-01-03 Thread PICCA Frederic-Emmanuel
Hello, I would like to discuss about this bug [1] I tryed to reproduce the scenary of piuparts in a virtual machine (gnome-box) installed in 3 steps: jessie base system mysql-server (I need a working database) tango-db (daemon) It works ok, I have a running tango-db daemon (ps aux |