Bug#887985: [libreoffice-mysql-connector] using mariadb, libreoffice-mysql-connector produces garbage in memofields

[Rene Engelhard <rene@debian.org>]

Hi,

On Mon, Jan 22, 2018 at 01:33:57PM +0100, Rene Engelhard wrote:
> LOL, if you don't look closely, yes. If you look closely there's no
> "upgrade".
> 
> That "mysql-connector-linux_4-3_x86_64.oxt" from above was done
> 
> 4.3
> Dec 22, 2014
> LibreOffice 4.3
> These are the mysql-connectors for x86 (32 bit) and x86-64 (64 bit) for linux.
> LGPL-v3+ (GNU Lesser General Public License Version 3 and later)
> final
> 
> So > 3 years ago, and only claims compatibility with LO 4.3 after all.
> 
> And I've no idea how/why they hacked up the version but what we build
> out of LibreOffice currently is the current version.
> 
> rene@rpi3:~/tmp/core/mysqlc$ grep version ./source/description.xml
> #<?xml version="1.0" encoding="UTF-8"?>
>     <version value="1.0.2" />
>          <OpenOffice.org-minimal-version value="3.3" d:name="OpenOffice.org 3.3"/>

That confusion already was there once:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836184

Let's look:

$ unzip mysql-connector-linux_4-3_x86_64.oxt 
Archive:  mysql-connector-linux_4-3_x86_64.oxt
   creating: META-INF/
  inflating: META-INF/manifest.xml   
  inflating: components.rdb          
  inflating: description-en-US.txt   
  inflating: description.xml         
 extracting: images/extension_32.png  
  inflating: libmysqlclient_r.so
             ^^^^^^^^^^^^^^^^^^^^
  inflating: libmysqlcppconn.so      
  inflating: mysqlc.uno.so           
   creating: registration/
  inflating: registration/LICENSE    
  inflating: registry/data/org/openoffice/Office/DataAccess/Drivers.xcu  
$ grep version description.xml 
<?xml version="1.0" encoding="UTF-8"?>
    <version value="1.0.4_3" />
         <OpenOffice.org-minimal-version value="3.3" d:name="OpenOffice.org 3.3"/>


Jup.

Was not able to find out the version of libmysqlcppconn.so though.

Of course on this "%/<S-F6>"" extensions website there's neither author
information nor source. So one can't even see whether something was changed or
whether MySQL vs. MariaDB is the only change. (and that 2 -> 4_3, most probably
resembling 4.3 of LO also is questionable.)

Now, using MariaDB instead of MySQL isn't a choice for stuff wanting to be in
a Debian release - I can't build against MySQL since MySQL (unless the policy
and/or default changes, as libmysqlclient was not/will not be in the release)
will not be in a release.

One can try to build libmysqlcppconn against mysql and see whether the bug
goes away, though. That then would make it either a libmysqlcppconn (or a
libmariadbclient bug.... Will try.

Regards,

Rene