Re: [Bacula-devel] Bug#2584: MySQL schema broken for MariaDB 10.5

2020-12-02 Thread Sven Hartge
On 30.11.20 13:14, Sven Hartge wrote: There is still ample time to get 11.x into Debian, so if you want to focus on that, this is fine. And by "ample time" I mean: It has to be in Unstable no later than 2021-01-11, when the first stage of the Release Freeze for Bullseye begins. After that w

Re: [Bacula-devel] Bug#2584: MySQL schema broken for MariaDB 10.5

2020-11-30 Thread Sven Hartge
On 30.11.20 13:04, Eric Bollengier via Bacula-devel wrote: I'm planing to do a new major release this week (11.0.0), and we can probably release a minor version for 9.6 as the same time. We still have a couple of issues with patches to review in the bug tracker. Please forgive me for speaking

Re: [Bacula-devel] Bug#2584: MySQL schema broken for MariaDB 10.5

2020-11-30 Thread Sven Hartge
On 30.11.20 13:04, Eric Bollengier via Bacula-devel wrote: On 2020-11-30 12:55, Sven Hartge wrote: Are there any plans for a timely 9.6.x maintenance release to publish the changes you made today? If not I will pull those as separate patches into the Debian package to keep Bacula fit for re

Re: [Bacula-devel] Bug#2584: MySQL schema broken for MariaDB 10.5

2020-11-30 Thread Eric Bollengier via Bacula-devel
Hello Sven, On 2020-11-30 12:55, Sven Hartge wrote: > On 30.11.20 09:16, Eric Bollengier via Bacula-devel wrote: > >> Thanks for the suggestions, we will fix the schema file following your >> tips, MySQL was not very strict in the past, now it is painful and >> difficult to get back on track. I g

Re: [Bacula-devel] Bug#2584: MySQL schema broken for MariaDB 10.5

2020-11-30 Thread Sven Hartge
On 30.11.20 09:16, Eric Bollengier via Bacula-devel wrote: Thanks for the suggestions, we will fix the schema file following your tips, MySQL was not very strict in the past, now it is painful and difficult to get back on track. I guess many programs will have the same kind of issues with such m

Re: [Bacula-devel] Bug#2584: MySQL schema broken for MariaDB 10.5

2020-11-30 Thread Sven Hartge
On 30.11.20 09:16, Eric Bollengier via Bacula-devel wrote: Thanks for the suggestions, we will fix the schema file following your tips, MySQL was not very strict in the past, now it is painful and difficult to get back on track. I guess many programs will have the same kind of issues with such m

Re: [Bacula-devel] Bug#2584: MySQL schema broken for MariaDB 10.5

2020-11-30 Thread Eric Bollengier via Bacula-devel
Hello Sven, Thanks for the suggestions, we will fix the schema file following your tips, MySQL was not very strict in the past, now it is painful and difficult to get back on track. I guess many programs will have the same kind of issues with such migration. Best Regards, Eric On 2020-11-28 17:5

Re: [Bacula-devel] Bug#2584: MySQL schema broken for MariaDB 10.5

2020-11-28 Thread Phil Stracchino
On 11/28/20 2:14 PM, Radoslav Bodó wrote: >> 3) Referenced Columns need to exist. >> >> BaseFiles.BaseJobId REFERENCES Job, but table Job does not contain >> BaseJobId, so this fails as well. > > It's not important for the root issue, but Sven insisted to comment that > anyway. To be complete I th

Re: [Bacula-devel] Bug#2584: MySQL schema broken for MariaDB 10.5

2020-11-28 Thread Radoslav Bodó
> 3) Referenced Columns need to exist. > > BaseFiles.BaseJobId REFERENCES Job, but table Job does not contain > BaseJobId, so this fails as well. It's not important for the root issue, but Sven insisted to comment that anyway. To be complete I think that point of BaseFiles.BaseJobId is to referen