On Tue, 25 Dec 2018 12:38:34 +0100 Luca Boccassi
wrote:
> On Tue, 25 Dec 2018 12:51:40 +0200 =?UTF-
8?B?T3R0byBLZWvDpGzDpGluZW4=?=
> wrote:
> > I did this change yesterday but have not uploaded yet as I'd like
to
> first
> > write an automated gitlab-ci.yml test in mariadb-10.3 to detect the
>
On Tue, 25 Dec 2018 12:51:40 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
wrote:
> I did this change yesterday but have not uploaded yet as I'd like to
first
> write an automated gitlab-ci.yml test in mariadb-10.3 to detect the
problem
> first.
>
>
I did this change yesterday but have not uploaded yet as I'd like to first
write an automated gitlab-ci.yml test in mariadb-10.3 to detect the problem
first.
https://salsa.debian.org/mariadb-team/mysql/commit/41b7e55f1c5a3cb93da2e2407230542cc9284222
On 12/24/18 8:18 PM, Otto Kekäläinen wrote:
> There is probably room to optimize things, but I cannot see that there
> would be a huge bug.
I guess looking at the FTBFS buildlogs from reproducible builds won't
change your assessment of the severity either.
Any of the affected packages will also
Severity: normal
There is probably room to optimize things, but I cannot see that there
would be a huge bug.
This "error" is visible only using aptitude. Normal apt-get will
resolve it just fine. And even with aptitude, you just select "yes" to
proceed with the suggested dependencies and it
On 12/24/18 12:59 PM, Otto Kekäläinen wrote:
> Severity: normal
Really? With so many affected packages?
> I am unable to reproduce this issue. Installing all of the mentioned
> packages works just fine.
Use the aptitude resolver:
# aptitude install default-libmysqlclient-dev
The following
.
Severity: normal
I am unable to reproduce this issue. Installing all of the mentioned
packages works just fine.
# dpkg -l | grep -iE 'maria|mysql|galera'
ii default-libmysqlclient-dev:amd64 1.0.4amd64
MySQL database development files (metapackage)
ii libmariadb-dev:amd64
7 matches
Mail list logo
