[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: suse open build service - debian builds
[Thread Prev] | [Thread Next]
- Subject: Re: suse open build service - debian builds
- From: Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
- Date: Wed, 11 Dec 2024 01:19:22 +0100
- To: user@xxxxxxxxxxxxxxxxxxxxxx
Le 11/12/2024 à 00:16, gbWilly a écrit :
... You see, no problems, unless things changed since 3.19.90.20241208+git64189e64. The date is download date and git short commit, when recipe was made. I build the packages past midnight, so on the 9th. and I made repo the evening of the 9th and installed it successfully. In the made .deb package archive the DEBIAN/control for gambas-gb-db- mysql and gambas-gb-db2-mysql depends on libmysqlclient21 (>= 8.0.11). I find it really strange to see your error after my own build going great. gbWilly
I find that strange too. Apparently it's only on OBS that the compilation fails.
But by looking at the code, I understood what I told in the previous mail: the version tests of 'gb.db.mysql' (and 'gb.db2.mysql' too) for the different connection constants only work with mysql. With MariaDB, it fails, by failing to compile or silently.
Regards, -- Benoît Minisini.
Re: suse open build service - debian builds | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
suse open build service - debian builds | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
Re: suse open build service - debian builds | T Lee Davidson <t.lee.davidson@xxxxxxxxx> |
Re: suse open build service - debian builds | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
Re: suse open build service - debian builds | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
Re: suse open build service - debian builds | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
Re: suse open build service - debian builds | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
Re: suse open build service - debian builds | Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx> |
Re: suse open build service - debian builds | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
Re: suse open build service - debian builds | gbWilly <gbWilly@xxxxxxxxxxxxxx> |