MariaDB 10.3 test packages should be removed from experimental. I
think it was just a temporary test by Ondrej. There is no point in
having a unreleased upstream version in Debian permantently.
I've reported this upstream at https://github.com/schani/metapixel/issues/10
Hello!
MariaDB 10.3 needs to be finalized and imported into Debian. After
that all the mess that are a fallout of a misfortunate upload of
mariadb-10.2 to Debian unstable will start to become resolved. Until
then we need to live with this, sorry.
2018-05-10 21:59 GMT+03:00 Emilio Pozuelo Monfort <po...@debian.org>:
> Hi Otto,
>
> On 10/05/18 20:24, Otto Kekäläinen wrote:
>> Hello!
>>
>> MariaDB 10.3 needs to be finalized and imported into Debian. After
>> that all the mess that are a fallout of a
to 14. kesäk. 2018 klo 9.57 Andy Li (a...@onthewings.net) kirjoitti:
..
> I'm sure you have been busy, but this issue has been there unfixed for
> several months.
> I would appreciate if you can spend a few minutes to answer our questions.
> If you lack the time to maintain the package, would you
su 17. kesäk. 2018 klo 10.27 Pirate Praveen (prav...@debian.org) kirjoitti:
>
> On Thu, 14 Jun 2018 15:57:18 +0800 Andy Li wrote:
> > I'm sure you have been busy, but this issue has been there unfixed for
> > several months.
> > I would appreciate if you can spend a few minutes to answer our
I have filed this upstream as well: https://jira.mariadb.org/browse/MDEV-14918
MariaDB RocksDB engine could start using this sst_dump binary when it
is available from rocksdb-tools. Currently it is still only in
experimental though.
This has been fixed in upstream master branch with the introduction of
CMAKE variable INSTALL_LIBDIR_DEB in commit
https://github.com/MariaDB/mariadb-connector-c/commit/eb64582b68eb627d70dffad8808c7b6d4cf11b27
I have tested it and works well. Will upload to Debian as part of
3.0.6 when it is
Control: tag -1 pending
Hello,
Bug #902729 in mariadb-connector-c reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #886756 in mariadb-10.1 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
Hello!
I plan to have this commit included in the next upload of MariaDB
10.1.x into Debian:
https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/89ae638d1d3b5a7157d086a9be2468cae764aae7
ti 9. tammik. 2018 klo 17.45 Jonas Meurer (jo...@freesources.org) kirjoitti:
>
> Package:
Hello!
ti 7. elok. 2018 klo 11.58 Jonas Meurer (jo...@freesources.org) kirjoitti:
>
> Am 07.08.2018 um 10:51 schrieb Jonas Meurer:
> > Hey Otto,
> >
> > Am 06.08.2018 um 23:09 schrieb Otto Kekäläinen:
> >> I plan to have this commit included in the next upload o
Hello!
la 30. kesäk. 2018 klo 1.15 James Clarke (jrt...@debian.org) kirjoitti:
>
> Package: libmariadb3
> Version: 1:3.0.3-2
> Severity: serious
>
> Hi,
> Trying to install libmariadb3 on a system which already has libmariadb2
> installed fails with:
>
> > Unpacking libmariadb3:amd64 (1:3.0.3-2)
Are you using encryption or compression in MariaDB which
percona-xtrabackup does not support? In that case you need
mariabackup: https://mariadb.com/kb/en/library/mariadb-backup-overview/
Otherwise I am not aware of any reasons percona-xtrabackup would not
work, it should.
It was not intended for the mariadb-10.x packages to ship the new LGPL
based client library. For that we have the separate
mariadb-connector-c package.
The package mariadb-10.2 is to be removed from Debian unstable and the
next versions of mariadb-10.3 uploaded to Debian will not include this
There is not enough maintenance power to maintain as many MariaDB
versions in Debian in parallel as we have now. The package
mariadb-10.2 is to be removed from Debian unstable and the security
update efforts will focus on quicker 10.1 and 10.3 uploads.
The package mariadb-10.2 was not supposed to ship the libmariadb-dev
package, which should come from mariadb-connector-c.
The package mariadb-10.2 is to be removed from Debian unstable and the
next versions of mariadb-10.3 uploaded to Debian will not include this
libmariadb-dev library.
This issue has been solved in MariaDB 10.3 packaging where package
name of mariadb-plugin-cracklib-password is correct and
breaks/replaces work as intended.
The packaging of mariadb-10.2 in Debian has a lot of errors and is
about to be removed from the unstable repository, and will eventually
be
This has been fixed in upstream, where libmariadb-dev ships
mariadb_config and libmariadb-dev-compat ships mysql_config. The
package libmariadb-dev-compat depends on libmariadb-dev, which in turn
breaks/replaces libmariadbclient-dev.
Please wait until mariadb-10.3 gets uploaded to Debian
Hello!
Here is the reply from the upstream author, manually forwarded as it
did not originally reach the issue address.
Forwarded Message
From: Georg Richter <ge...@mariadb.com>
To: Otto Kekäläinen <o...@mariadb.org>
Subject: Re: Connector/C with patch reported in
la 29. jouluk. 2018 klo 9.36 Scott Kitterman (deb...@kitterman.com) kirjoitti:
> > > I did add a symlink as in the attached patch and postfix builds again. I
> > > don't have a good way to do run-time testing, so I don't know if there are
> any
> > > further changes needed, but this at least
Hello!
As a side note, did you already test mariabackup from binary package
mariadb-backup (from source package mariadb-10.3)?
It is a fork of percona-xtrabackup with additional features so it
supports the latest versions of MariaDB Server and Galera.
Control: tag -1 pending
Hello,
Bug #917266 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Severity: normal
Seems mytop has been removed from Debian Testing in June 2017 and
there has not been any new uploads in 2 years. De-prioritizing the
removal of mytop from MariaDB due to this reason.
One option would of course be to split mytop into a separate binary
package built from the
Control: tag -1 pending
Hello,
Bug #863675 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
ti 25. jouluk. 2018 klo 21.31 Sebastiaan Couwenberg
(sebas...@xs4all.nl) kirjoitti:
...
> > I cannot reproduce this inside a Docker image (e.g. via Salsa
> > gitlab-ci.yml) because the operation is too heavy, but basically this
> > bug report is about how aptitude resolves build dependencies and
pe 4. tammik. 2019 klo 18.31 gregor herrmann (gre...@debian.org) kirjoitti:
>
> On Fri, 04 Jan 2019 00:22:54 +0100, gregor herrmann wrote:
>
> > I've now pinged the upstream issue at:
> > https://github.com/perl5-dbi/DBD-mysql/issues/275
>
> And they plan to try and fix the issue:
>
> Can't you just use dh_link to add a symlink?
I am re-evaluating this fix and considering to revert it. The problem
with Postfix was that it did not find /usr/include/mysql/mysql.h and
we added a symlink in libmariadb-dev to fix it.
However, this symlink already existed in
Hello!
ke 23. tammik. 2019 klo 16.45 Giovanni Mascellani (g...@debian.org) kirjoitti:
>
> Hi,
>
> the failure is apparently due to insufficient timeout time for some
> tests. Some mipsel builders are more powerful, therefore manage to go
> through all the tests without problems, but other are
Hello!
ke 23. tammik. 2019 klo 19.49 Scott Kitterman (deb...@kitterman.com) kirjoitti:
>
> On Wednesday, January 23, 2019 05:32:49 PM Otto Kekäläinen wrote:
> > > Can't you just use dh_link to add a symlink?
> >
> > I am re-evaluating this fix and considerin
Control: tag -1 pending
Hello,
Bug #914112 in galera-3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #914112 in galera-3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
> Just submitted a merge request on Salsa. Thanks for the clear documentation
> on how to set up the CI pipeline in my forked repo. One issue I noticed,
> though, is that the GitLab CI configuration file is called
> debian/.gitlab-ci.yml, while it's debian/gitlab-ci.yml in the other MariaDB
>
Control: tag -1 pending
Hello,
Bug #863675 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #863675 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
.
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
Control: tag -1 pending
Hello,
Bug #917075 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hello!
Can you please provide an actual pbuilder command or something I can
copy-paste to reproduce the actual problem (and not just the aptitude
symptom)?
Control: tag -1 pending
Hello,
Bug #917075 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
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
Hello!
ti 25. jouluk. 2018 klo 10.06 Scott Kitterman (deb...@kitterman.com) kirjoitti:
> Severity: grave
> Justification: renders package unusable
>
> no longer found.
>
> Since mariadb10.3 became the default this no longer works:
>
> #include
>
> It has to be changed to:
>
> #include
>
> You
Source: mysql-defaults
Version: 1.0.5
Severity: serious
Justification: makes the package in question unusable or mostly so
The package has been updated to depend on Mariadb 10.3, which is
currently available only in Debian unstable. This serious bug report
is done to prevent mysql-defaults from
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
Control: tag -1 pending
Hello,
Bug #886853 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
I made this extension to the gitlab-ci.yml file to be able to
automatically test for issues like this in the future:
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/0ec004b4e4fc7c98a7b16cbe1a821be12ace1110
Ideally it would actually also attempt to build something first with
MySQL and
Control: tag -1 pending
Hello,
Bug #863675 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #863675 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
ti 25. jouluk. 2018 klo 10.17 Sebastiaan Couwenberg
(sebas...@xs4all.nl) kirjoitti:
>
> On 12/25/18 8:57 AM, Otto Kekäläinen wrote:
> > Can you please provide an actual pbuilder command or something I can
> > copy-paste to reproduce the actual problem (and not just the ap
Control: tag -1 pending
Hello,
Bug #909181 in mariadb-connector-c reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
For the records of this bug report and people following it, there are a lot
of discussions going on in both
https://github.com/perl5-dbi/DBD-mysql/issues/275 and
https://github.com/MariaDB/mariadb-connector-c/pull/95
I will now import MariaDB 10.3.12 into
Hello!
gregor herrmann kirjoitti pe 4. tammikuuta 2019 klo
1.23:
> On Thu, 03 Jan 2019 22:04:48 +0200, Otto Kekäläinen wrote:
>
> > Just checking: are you Georg or Gregor currently working on this
> > issue, and do you have any estimate when we could expect either a
&g
Hello!
pe 28. jouluk. 2018 klo 11.09 Georg Richter (ge...@mariadb.com) kirjoitti:
>
> Hi Otto,
>
> no clue about dbd-mysql - we reported several bugs (and sent fixes), but
> didn't get feedback since more than a year. Why don't you ship DBD-mariadb
> instead?
Gregor Hermann, do you want to
Control: tag -1 pending
Hello,
Bug #863675 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
onnect bug:
>
> Latest code is setting the reconnect flag correctly via mysql_options
> (instead of accessing internal member), so I need to debug why it's failing.
>
> /Georg
>
> On Fri, Dec 28, 2018 at 1:31 PM gregor herrmann wrote:
>>
>> On Fri, 28 Dec 201
Now with the mysql version fixed the mariadb version regressed. Does any of
you spot what is the failure cause in
https://ci.debian.net/data/autopkgtest/testing/amd64/libd/libdbd-mariadb-perl/1690599/log.gz
?
MariaDB 10.3 overview at https://tracker.debian.org/pkg/mariadb-10.3
Otto Kekäläinen
Hello!
pe 28. jouluk. 2018 klo 15.33 Scott Kitterman (deb...@kitterman.com) kirjoitti:
>
> I did add a symlink as in the attached patch and postfix builds again. I
> don't have a good way to do run-time testing, so I don't know if there are any
> further changes needed, but this at least fixes
The packages libmaraidbclient-dev and libmysqlclient-dev were in
Conflicts with each other and not co-installable. We should probably
have the same libmariadb-dev vs libmysqlclient-dev as well.
Feel free to open a merge request on Salsa for whatever change to want
to have in the packaging. I
Alternatively, the mentioned files could be moved to
libmariadb-dev-compat but that would require some tweaking to the
manpage names etc as currently the mariadb-config.1 does not have it's
own file but is a symlink to mysql-config.1 (unlike how the
libmariadb-dev-compat version 3.0.7 in unstable
Hello!
Feel free to open a merge request on Salsa for whatever change to want
to have in the packaging. I wrote instructions with screenshots at
https://wiki.debian.org/Teams/MySQL/patches so it would be as easy as
possible to contribute.
I am also grateful for meta-contributions to the
Hello!
Could you please check if it is still valid and happening in Debian
unstable there has had several updates MariaDB client libraries /
connector C libraries recently?
Thanks!
Hello!
Can you please update the dependency to libmariadbd19, as that has
superceeded the older ..18 version in Debian unstable/Buster? Thanks!
Control: tags -1 moreinfo
Hello!
This bug you reported is rather old:
https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no=849630
Could you please check if it is still valid and happening in Debian
unstable that has had several updates to both MariaDB and Perl
libraries recently?
Thanks!
Hello!
> > > I happened upon #921599 at $work and saw you tagged it as pending,
> > > so I wondered if there are commits to the git repo on salsa or a merge
> > > request or something where this bug is fixed?
> > This is the PR https://github.com/MariaDB/mariadb-connector-c/pull/101
> > and this
Hello!
Could you please check if libmyodbc works if built against libmariadb3
instead of libmysqlclient18 ?
That would be a nice way to solve it.
If you have tried this in the past, could you pleas retry it now as
Debian unstable has had several updates to both MariaDB and Perl
libraries
Hello!
Could you please check if it is still valid and happening in Debian
unstable there has been several updates MariaDB client libraries /
connector C libraries recently?
Thanks!
Hello!
Could you please check if it is still valid and happening in Debian
unstable there has had several updates MariaDB client libraries /
connector C libraries recently?
Thanks!
Hello!
Can you please test again with the latest version in Debian unstable
and verify this is fixed now?
MariaDB 10.3 in Debian has a rather extensive testing suite at
https://salsa.debian.org/mariadb-team/mariadb-10.3/pipelines/41873
If you would like to contribute and write a new section to
OK, so current MariaDB 10.3.13 we have in Debian contains MariaDB
Connector C 3.0.9
mariadb-10.3$ grep -rF 'SET(CPACK_PACKAGE_VERSION_' libmariadb/CMakeLists.txt
SET(CPACK_PACKAGE_VERSION_MAJOR 3)
SET(CPACK_PACKAGE_VERSION_MINOR 0)
SET(CPACK_PACKAGE_VERSION_PATCH 9)
This has been fixed upstream
Control: tag -1 pending
Hello,
Bug #910902 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #925117 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #925117 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #910902 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #925117 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #910902 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #925117 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #910902 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hello!
> What I see, you do not run autopkgtest within the pipelines. In my
> understanding, this test should go to a autopkgtest. I'll add it to my TODO
> list, to write such an test for mariadb, when I'm writing autopkgtest for
> akonadi.
We do run: see
Control: tag -1 pending
Hello,
Bug #921488 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #921488 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tags -1 +moreinfo
Hello!
> mariadb moved my_print_defaults from mysql-server-core to mariadb-server.
> So akonadi-backend-mysql do now need to depend at mariadb-server. As
> "my_print_defaults" is only needed at first start of akonadi it is a pity if
> we
> would that for now rely on a
Potentially related:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916375 apache2:
Segmentation fault when mod_perl.so is enabled
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918988
libmysqlclient symbol conflict segfaulted Apache
-
Looks like this has never been in the core package:
https://packages.debian.org/search?searchon=contents=resolveip=path=unstable=any
/usr/bin/resolveipmariadb-server-10.0 [arm64], mariadb-server-10.1
[powerpc], mariadb-server-10.3 [ei ia64, powerpc, s390, sparc],
mariadb-server-5.5 [sparc,
Control: tags -1 moreinfo
Hello!
Can you still reproduce this with latest versions of MariaDB 10.3.13
and mod_perl ?
Fix for this pending at
https://salsa.debian.org/mariadb-team/mariadb-10.3/commits/bugfix/910902-move-resolveip-to-server-core
Control: tag -1 pending
Hello,
Bug #925117 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #925117 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Thanks!
Control: tag -1 pending
Hello,
Bug #910902 in mariadb-10.3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hello!
The OpenSSL licence will change from 3.0.0 onwards
(https://www.openssl.org/source/license.html) but you are right that
for version 1.1.1 the SSLeay clause applies. MySQL and MariaDB has the
OpenSSL exception, and YaSSL has been used due to earlier
interpretation by non-maintainers that it
Control: tag -1 pending
Hello,
Bug #920209 in galera-3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
su 20. tammik. 2019 klo 14.42 Andreas Beckmann (a...@debian.org) kirjoitti:
...
> -rwxr-xr-x 1 root root 14840 Jan 8 21:52 /usr/bin/mariadb_config
> lrwxrwxrwx 1 root root14 Jan 8 21:52 /usr/bin/mysql_config ->
> mariadb_config
> lrwxrwxrwx 1 root root17 Jan 8 21:52
>
su 20. tammik. 2019 klo 16.21 Andreas Beckmann (a...@debian.org) kirjoitti:
>
> On 2019-01-20 13:39, Andreas Beckmann wrote:
> > Could we please have the symlinks in one direction only?
>
> There is also this Lintian warning:
> W: mariadb-10.3 source: binaries-have-file-conflict libmariadb-dev
>
FYI: I decided to revert this commit in
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/71cada820618e00f88325c6e575ed5149eaa9455
We have quite extensive CI that has not spotted any regressions, but indeed
the CI would be even more perfect if it included a 3rd party build test,
e.g.
su 20. tammik. 2019 klo 14.21 Andreas Beckmann (a...@debian.org) kirjoitti:
> Followup-For: Bug #863675
> Control: reopen -1
> Control: found -1 1:10.3.12-1
>
> So, which package is shipping /usr/bin/mysql_config ?
> libmariadb-dev (which got the B+R added) or libmariadb-dev-compat ?
>
>
su 14. huhtik. 2019 klo 14.06 peter green (plugw...@p10link.net) kirjoitti:
>
> Could you please check if it is still valid and happening in Debian
> unstable there has had several updates MariaDB client libraries /
> connector C libraries recently?
>
> According to
>
For the record some debug output:
### Stretch before upgrade
# dpkg -S /usr/lib/x86_64-linux-gnu/libma* /usr/lib/x86_64-linux-gnu/libmy*
libmagic1:amd64: /usr/lib/x86_64-linux-gnu/libmagic.so.1
libmagic1:amd64: /usr/lib/x86_64-linux-gnu/libmagic.so.1.0.0
libmailutils5:amd64:
### Buster
# dpkg -S /usr/lib/x86_64-linux-gnu/libma* /usr/lib/x86_64-linux-gnu/libmy*
libmariadb-dev: /usr/lib/x86_64-linux-gnu/libmariadb.so
libmariadb3:amd64: /usr/lib/x86_64-linux-gnu/libmariadb.so.3
libmariadb-dev: /usr/lib/x86_64-linux-gnu/libmariadbclient.a
libmariadb-dev:
> The mariadb-10.1 on security.debian.org fails to build on all mipsen, with
> similar errors:
>
> > [ 99%] Linking CXX executable explain_filename-t
> > cd /<>/builddir/unittest/sql && /usr/bin/cmake -E
> > cmake_link_script CMakeFiles/explain_filename-t.dir/link.txt --verbose=1
> >
> Justification: fails to build from source (but built successfully in the past)
> The mariadb-10.1 package on security.d.o doesn't build on s390x, one test
> fails:
Unfortunately there are no public build logs of this available at
It seems this was fixed in
https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/60b9d396b7712c46924564c6a73a0c02ff88f0ed
101 - 200 of 360 matches
Mail list logo
