Bug#920365: mariadb_config: improve cross compilation support

Hi, Helmut! So, there's nothing for us (upstream) to do here? pkg-config just works and you already have the script? Regards, Sergei On Aug 16, Helmut Grohne wrote: > Hi Sergei, > > On Fri, Aug 16, 2019 at 05:41:14PM +0200, Sergei Golubchik wrote: > > Ok. Two thoughts. Fir

Bug#920365: mariadb_config: improve cross compilation support

Hi, Helmut! On Aug 13, Helmut Grohne wrote: > > On Sat, Jan 26, 2019 at 07:37:14PM +0100, Sergei Golubchik wrote: > > I would say that when cross-compiling mariadb_config should be built > > for the host architecture. > > That is the status quo, but I guess you're c

Bug#919373: libmariadb-dev-compat: lacks MYSQL_SERVER_VERSION causing FTBFS

Already fixed in 10.3.13 (libmariadb v3.0.9) Regards, Sergei

Bug#920365: mariadb_config: improve cross compilation support

Hi, Helmut! I don't think I understand what's happening. I would say that when cross-compiling mariadb_config should be built for the host architecture. You'll get "Exec format error" if you run'll run it on the target architecture, but that should not be a problem, as you will not need to run m

Bug#888392: [debian-mysql] Bug#888392: Bug#888392: Bug#888392: mariadb-connector-c: FTBFS on non-Linux: version script unused

Hi, Otto! On Dec 11, Otto Kekäläinen wrote: > Hello Aaron! > > If the solution is evident to you, can you perhaps make a pull request > on Salsa (https://wiki.debian.org/Teams/MySQL/patches) or even > upstream? IF(Linux) was added six years ago in v2.2.1, before even version script was used. It

Bug#536726: Regarding CVE-2009-2446: Problems with COM_CREATE_DB etc.

re > necessary. This is our fix for 5.0: http://lists.mysql.com/commits/77649 you probably won't be able to see the bug itself, it's private until the released version will be out. But according to comments the fix was pushed to 5.0.84 Regards / Mit vielen Grüßen, Sergei -- __ ___

Bug#375694: Bug #20729 security relevant?

someone could confirm that my self written > patch does no more harm than cure :)) Done. Regards, Sergei -- __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer /

Bug#359701: Debian needs patch for CVE-2006-0903 for MySQL 3.23

anyway. (though you may want to keep in mind that until bug status is 'Patch Approved', 'Documenting', or 'Closed' the patch you see is not necessarily final) Regards, Sergei -- __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PR

Bug#306409: Debian needs your help :) (CAN-2005-0711 backport breaks isam/create.c)

ndef O_NOFOLLOW #define O_NOFOLLOW 0 #endif But as it's your custom patch, and it's only for Debian - where you can know for sure that O_NOFOLLOW exists - you can safely drop O_EXCL. But then I'd suggest to remove this #ifdef above. To be on the safe side :) Regards, Sergei --