Re: [Libreoffice-qa] Bug 59481 - FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0
On Mon, 2013-01-21 at 17:55 +0100, Lionel Elie Mamane wrote: On Sat, Jan 19, 2013 at 11:17:20AM -0500, Terrence Enger wrote: How would this compare in effort and benefit to the job of making the mysql extension work with LibreOffice 4.0? The MySQL extension just needs to be compiled/linked against LibreOffice 4.0; then it should work. No development work needed. Only building (for GNU/Linux and MacOS (if necessary): on an OS install as old as what the extension wants to be compatible with). So, here's how it compares in effort and benefit, it being the stuff described in the ESC minutes that you linked to. - MUCH more work - MUCH more benefit, since it would allow the MySQL SDBC connector to be bundled with LibreOffice. I will *gladly* review a patch that does that! That sounds too ambitious for me to work on usefully. I shall have to look for smaller tasks. BTW, I have not been simply ignoring you; for four weeks I had only fleeting, intermittent connection to the internet. Terry. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Bug 59481 - FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0
On Sat, Jan 19, 2013 at 11:17:20AM -0500, Terrence Enger wrote: On Fri, 2013-01-18 at 08:04 -0800, Joel Madero wrote: Can someone triage this one? Thanks in advance! And there has been quit a bit of subsequent discussion. I wonder just what Lionel was proposing [1] after the announcement [2] of changed licence for the mariadb / mysql client library. I was commenting that for LibreOffice, this is not sufficient. We, as a project, have decided not to ship (binaries compiled from) GPL code in our main product, that is LibreOffice (we do ship GPL code that does not end up in LibreOffice, e.g. in http://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/make-3.82-gbuild ). The MySQL native (SDBC) connector is made as follows:: MySQL SDBC connector itself (SISSL / Apache / LGPL licence, depending on version) using MySQL Connector/C++ (GPL) using MySQL Connector/C (AKA libmysql or client Library) (GPL) Swapping out the MariaDB client library for the MySQL client library brings the picture to: MySQL SDBC connector itself using MySQL Connector/C++ (GPL) using libmariadb (LGPL) So still not OK for integration into LibreOffice proper, because still a GPL component. For us to be able to ship the MySQL SDBC connector (with our current self-imposed policy), one of these things has to be done: 1) Write an Apache/BSD/LGPL/... licensed clone of MySQL Connector/C++ OR 2) Change the MySQL SDBC connector to not need MySQL Connector/C++, but use libmysql/libmariadb directly (these are API-compatible; we would ship with libmariadb, but if a downstream user would want to swap it with libmysql, technically there should be no problem) But that's only *our* policy. Any third party can make a different choice, and e.g. Debian has made another choice and *does* ship GPL code, including the MySQL Connector/C++ and the MySQL SDBC connector for use with LibreOffice. It is my understanding any such third party would be allowed to upload the MySQL SDBC connector for use with LibreOffice to extensions.libreoffice.org; I don't see on that website a policy that forbids that. If any such third party would do that, at least for Microsoft Windows and MacOS X, I believe it would make some of our users happier. How would this compare in effort and benefit to the job of making the mysql extension work with LibreOffice 4.0? The MySQL extension just needs to be compiled/linked against LibreOffice 4.0; then it should work. No development work needed. Only building (for GNU/Linux and MacOS (if necessary): on an OS install as old as what the extension wants to be compatible with). So, here's how it compares in effort and benefit, it being the stuff described in the ESC minutes that you linked to. - MUCH more work - MUCH more benefit, since it would allow the MySQL SDBC connector to be bundled with LibreOffice. I will *gladly* review a patch that does that! Just by the way, does this change of licence return mysql to consideration for LO's built-in database [4]? No, because this is only the client library, not the database engine itself. For our embedded database, we want to ship a database engine. The database engine is still GPL. Be it MySQL or MariaDB. -- Lionel ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Bug 59481 - FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0
On 01/21/2013 11:55 AM, Lionel Elie Mamane wrote: On Sat, Jan 19, 2013 at 11:17:20AM -0500, Terrence Enger wrote: On Fri, 2013-01-18 at 08:04 -0800, Joel Madero wrote: Can someone triage this one? Thanks in advance! And there has been quit a bit of subsequent discussion. I wonder just what Lionel was proposing [1] after the announcement [2] of changed licence for the mariadb / mysql client library. I was commenting that for LibreOffice, this is not sufficient. We, as a project, have decided not to ship (binaries compiled from) GPL code in our main product, that is LibreOffice (we do ship GPL code that does not end up in LibreOffice, e.g. in http://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/make-3.82-gbuild ). The MySQL native (SDBC) connector is made as follows:: MySQL SDBC connector itself (SISSL / Apache / LGPL licence, depending on version) using MySQL Connector/C++ (GPL) using MySQL Connector/C (AKA libmysql or client Library) (GPL) Swapping out the MariaDB client library for the MySQL client library brings the picture to: MySQL SDBC connector itself using MySQL Connector/C++ (GPL) using libmariadb (LGPL) So still not OK for integration into LibreOffice proper, because still a GPL component. For us to be able to ship the MySQL SDBC connector (with our current self-imposed policy), one of these things has to be done: 1) Write an Apache/BSD/LGPL/... licensed clone of MySQL Connector/C++ OR 2) Change the MySQL SDBC connector to not need MySQL Connector/C++, but use libmysql/libmariadb directly (these are API-compatible; we would ship with libmariadb, but if a downstream user would want to swap it with libmysql, technically there should be no problem) But that's only *our* policy. Any third party can make a different choice, and e.g. Debian has made another choice and *does* ship GPL code, including the MySQL Connector/C++ and the MySQL SDBC connector for use with LibreOffice. It is my understanding any such third party would be allowed to upload the MySQL SDBC connector for use with LibreOffice to extensions.libreoffice.org; I don't see on that website a policy that forbids that. If any such third party would do that, at least for Microsoft Windows and MacOS X, I believe it would make some of our users happier. Then perhaps it is time to reconsider *your* policy. Or, perhaps you should explain to us what problem does the GPL license present to LibreOffice? This seems a little hypocritical. You will not include GPL licensed code in LO that you make available for download. Yet, the same website can contain extensions that include GPL licensed code. As a result, we the users of LO may have to use inferior software in the extensions because you will not provide us with a good SDBC to connect to MySQL or MariaDB. There is another possibility: provide a JDBC that can be used. Is there a license problem with that also? I know there is a potential Java problem. --Dan How would this compare in effort and benefit to the job of making the mysql extension work with LibreOffice 4.0? The MySQL extension just needs to be compiled/linked against LibreOffice 4.0; then it should work. No development work needed. Only building (for GNU/Linux and MacOS (if necessary): on an OS install as old as what the extension wants to be compatible with). So, here's how it compares in effort and benefit, it being the stuff described in the ESC minutes that you linked to. - MUCH more work - MUCH more benefit, since it would allow the MySQL SDBC connector to be bundled with LibreOffice. I will *gladly* review a patch that does that! Just by the way, does this change of licence return mysql to consideration for LO's built-in database [4]? No, because this is only the client library, not the database engine itself. For our embedded database, we want to ship a database engine. The database engine is still GPL. Be it MySQL or MariaDB. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Bug 59481 - FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0
Hello Dan, I have reported https://bugs.freedesktop.org/show_bug.cgi?id=59481 (FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0) and https://bugs.freedesktop.org/show_bug.cgi?id=59516 (FILEOPEN: Native MySQL-connector couldnt be installed under Windows in LO 4.0) I looked through the bugs reports for possible duplication. I found 59481 (Linux 32 bit RPM) which is this one, 59533 (Windows 32 bit), and 59516 (Windows 32 bit). All of them have the same problem: the MySQL native connector can not be used to connect to a MySQL data source. I use Ubuntu 12.04 LTS 32 bit, and I have the same problem with the MySQL native connector. My conclusion is that the 32 bit version of it has a regressive bug. I can use this connector with LO 3.5.7.2 and 3.6.4.3 but not 4.0.0.1RC. Being new at this, should I change Platform to All for 59481? Should 59533 and 59516 be marked as duplicates? Should I mark 59481 as confirmed? I believe that these are the things that need to be done. There is a difference in the behavior under Linux and Windows. The old connector 1.0.1 doesn't work under Linux since 3.5. So you could only connect with the 1.1.0 of AOO. Under Linux this connector could be installed in LO 4.0.0.1 rc. Under Windows the installation fails. Linux-user might think: Connector is installed, no error appears, should work - but it doesn't: ... No SDBC driver was found for the given URL. First I thought it was the same problem at Windows, but it wasn't (I have no Window here at all, so it is reported from other persons by mail to me). So I have to report another bug. See https://bugs.freedesktop.org/show_bug.cgi?id=59481#c1 Only one bug in one report I have often heard. So I linked this two reports with See also ... Bug 59533 is a duplicate of 59516. Don't know, why the reporter is writing a new bug. He always noticed bug 59481 and then he could also notice the link to bug 59516. I will mark this report as a duplicate. Regards Robert ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Bug 59481 - FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0
On 01/19/2013 03:43 AM, Robert Großkopf wrote: Hello Dan, I have reported https://bugs.freedesktop.org/show_bug.cgi?id=59481 (FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0) and https://bugs.freedesktop.org/show_bug.cgi?id=59516 (FILEOPEN: Native MySQL-connector couldnt be installed under Windows in LO 4.0) I looked through the bugs reports for possible duplication. I found 59481 (Linux 32 bit RPM) which is this one, 59533 (Windows 32 bit), and 59516 (Windows 32 bit). All of them have the same problem: the MySQL native connector can not be used to connect to a MySQL data source. I use Ubuntu 12.04 LTS 32 bit, and I have the same problem with the MySQL native connector. My conclusion is that the 32 bit version of it has a regressive bug. I can use this connector with LO 3.5.7.2 and 3.6.4.3 but not 4.0.0.1RC. Being new at this, should I change Platform to All for 59481? Should 59533 and 59516 be marked as duplicates? Should I mark 59481 as confirmed? I believe that these are the things that need to be done. There is a difference in the behavior under Linux and Windows. The old connector 1.0.1 doesn't work under Linux since 3.5. So you could only connect with the 1.1.0 of AOO. Under Linux this connector could be installed in LO 4.0.0.1 rc. Under Windows the installation fails. Linux-user might think: Connector is installed, no error appears, should work - but it doesn't: ... No SDBC driver was found for the given URL. OK, I understand. Perhaps this points to a possible bug in the Extension Manager itself. The AOO version of this connector seems to install, but it fails to enable the connector. I have clicked the connector, and two buttons appear: Enable and Delete. When I click the Enable button, I get the error message. Seems to me that installing an extension should also enable it. Then if someone wants to disable an extension, he can open the Extension Manager to do this. This might be a bug, or is it a feature request? --Dan First I thought it was the same problem at Windows, but it wasn't (I have no Window here at all, so it is reported from other persons by mail to me). So I have to report another bug. See https://bugs.freedesktop.org/show_bug.cgi?id=59481#c1 Only one bug in one report I have often heard. So I linked this two reports with See also ... Bug 59533 is a duplicate of 59516. Don't know, why the reporter is writing a new bug. He always noticed bug 59481 and then he could also notice the link to bug 59516. I will mark this report as a duplicate. Regards Robert ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/ ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Bug 59481 - FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0
On 01/19/2013 01:27 PM, Dan Lewis wrote: Hi all, OK, I understand. Perhaps this points to a possible bug in the Extension Manager itself. The AOO version of this connector seems to install, but it fails to enable the connector. I have clicked the connector, and two buttons appear: Enable and Delete. When I click the Enable button, I get the error message. Seems to me that installing an extension should also enable it. Then if someone wants to disable an extension, he can open the Extension Manager to do this. This might be a bug, or is it a feature request? IMHO it is a bug because it was decided at one stage that compatibility should be maintained with the Oracle mysql connector precisely because it wasn't going to be, or couldn't be (for whatever reasons) integrated into the LO default build. However, it was later decide that 4.0 would allow for ABI breakage. This meant that the devs recognized that some extensions would probably break and that it would be OK. They also stated that it would be up to extension providers to correct their extensions so that they would work with the new version of LO. Now of course, if one takes that attitude, it would be up to the AOO guy providing the Oracle AOO connector, already outside of the official AOO project, to align his extension code so that it worked with LO - yeah, right, like that is really going to happen...it might, if similar changes get pushed into the AOO code that also cause ABI breakage, thus forcing the AOO connector provider to update the code. At the moment, though, unlikely. Alternatively, it is up to the Linux distribs to provide testing versions of the connector that are ABI compatible with LO. This simply doesn't happen at the moment, again, for whatever reason. It will only happen when a distrib upgrades the version of LO it provides, and only then if it remembers to upgrade all the added-on bits at the same time. However, since for Mac OSX and Windows, there is no federating distrib manager, these 2 OS groups are on their own, in other words, stuffed. Alex ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Bug 59481 - FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0
On Fri, 2013-01-18 at 08:04 -0800, Joel Madero wrote: Can someone triage this one? Thanks in advance! And there has been quit a bit of subsequent discussion. I wonder just what Lionel was proposing [1] after the announcement [2] of changed licence for the mariadb / mysql client library. How would this compare in effort and benefit to the job of making the mysql extension work with LibreOffice 4.0? Just by the way, does this change of licence return mysql to consideration for LO's built-in database [4]? Terry. References -- [1] http://lists.freedesktop.org/archives/libreoffice/2012-December/042293.html minutes of ESC call Search for LGPL [2] http://openquery.com/blog/mariadb-client-libraries-end-duallicensing Reporting 503 - Service Not Available as I write this. [4] https://bugs.freedesktop.org/show_bug.cgi?id=51781 fdo# 51781 Select a good replacement for embedded HSQLDB 1.8 ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Bug 59481 - FILEOPEN: Linux rpm: Native MySQL-connector aoo-my-sdbc-1.1.0 didn't work any more with LO 4.0
On 01/18/2013 11:04 AM, Joel Madero wrote: Can someone triage this one? Thanks in advance! Best Regards, Joel I looked through the bugs reports for possible duplication. I found 59481 (Linux 32 bit RPM) which is this one, 59533 (Windows 32 bit), and 59516 (Windows 32 bit). All of them have the same problem: the MySQL native connector can not be used to connect to a MySQL data source. I use Ubuntu 12.04 LTS 32 bit, and I have the same problem with the MySQL native connector. My conclusion is that the 32 bit version of it has a regressive bug. I can use this connector with LO 3.5.7.2 and 3.6.4.3 but not 4.0.0.1RC. Being new at this, should I change Platform to All for 59481? Should 59533 and 59516 be marked as duplicates? Should I mark 59481 as confirmed? I believe that these are the things that need to be done. --Dan ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
