tag 836185 - patch close 836185 1:5.1.2~rc2-1 thanks Hi,
On Wed, Aug 31, 2016 at 05:57:52PM +0800, Rolf Leggewie wrote: > the libreoffice-mysql-connector bug script is faulty. This leads to an > error when reporting a bug with reportbug. Well, that isn't exactly your bug but yes, the script was faulty. Already fixed with https://anonscm.debian.org/cgit/pkg-openoffice/libreoffice.git/commit/libreoffice-mysql-connector.bug-script.in?id=aeaf73859aee6fc7fd1a596103a093d850470fe6 (though admittedly not in stable) > Author: Rolf Leggewie <f...@rolf.leggewie.biz> > Subject: fix bug script in libreoffice-mysql-connector > > --- new/libreoffice-mysql-connector.bug-script.in 2016-08-31 > 17:53:49.446917134 +0800 > +++ orig/libreoffice-mysql-connector.bug-script.in 2016-08-31 > 17:53:14.422743461 +0800 > @@ -1,2 +1,2 @@ > #!/bin/sh > -/usr/lib/libreoffice/program/unopkg list --bundled mysql-connector-ooo >&3 > +/usr/lib/libreoffice/program/unopkg list --bundled > com.sun.star.mysql-connector-ooo-@PLATFORMID@ >&3 Interesting, where do you get the "mysql-connector-ooo" thing from? See https://anonscm.debian.org/cgit/pkg-openoffice/libreoffice.git/log/libreoffice-mysql-connector.bug-script.in. There was no version without com.sun.star Yes, not even in https://anonscm.debian.org/cgit/pkg-openoffice/libreoffice.git/tree/libreoffice-mysql-connector.bug-script.in?h=debian-jessie-4.3.3 And there's no trace of it in the actual package either: # dpkg -l libreoffice-mysql-connector Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-================================= ii libreoffice-my 1.0.2+LibO4. amd64 MariaDB/MySQL Connector extension # cat /usr/share/bug/libreoffice-mysql-connector/script #!/bin/sh /usr/lib/libreoffice/program/unopkg list --bundled com.sun.star.mysql-connector-ooo-$PLATFORMID >&3 Anyway, the bug script _was_ flaky (though differently) and was fixed. Maybe this could be included in a subsequent stable update (if that one happens except for stuff coming from -security...), but I doubt the RT will deem it as important enough (I don't either.) Regards, Rene
