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.
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
> 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
su 20. tammik. 2019 klo 1.44 Andreas Beckmann (a...@debian.org) kirjoitti:
>
> On 2019-01-19 21:14, Andreas Beckmann wrote:
> > Getting back to the current case: I assume this is caused by
> > libmariadbclient-dev being turned into a virtual package provided by
> > libmariadb-dev. I'll test
er backwards
compatibility? How do you suggest this is resolved?
Below is the file listing I sent you on December 10th, which I did not
get much replies to. Maybe you want to re-review it and comment if
something is misplaced?
ti 11. jouluk. 2018 klo 10.38 Otto Kekäläinen (o...@debian.org) kirjoi
-- Forwarded message -
From: Sergei Golubchik
Hi, Otto!
On Jan 15, Otto Kekäläinen wrote:
> Hello!
>
> Introducing MariaDB 10.3 (and the libmaraidb3 it includes) changed
> somewhat how packages build compared to MariaB 10.1. In effect there
> are bunch of regre
(Regarding https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395
and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919374)
One of the failures is due to not finding header file mysql_time.h
In Debian stable and testing the file
/usr/include/mysql/mysql_time.h is provided by
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!
> > The postinst of Mroong install is, and the postrm uninstalls it
> > correctly. There is however no code that would on a
> > postinst/preinst/upgrade scenario reinstall the plugin if the path has
> > changed (eg. as it does on in MariaDB 10.3 when the soname path
> > updates from
Control: tag -1 wontfix
To get any progress with this issue, please collaborate with upstream.
Consider for example paying them to fix their issue #313.
> Forwarded: https://github.com/codership/galera/issues/313
>
> Hello!
>
> This looks like a duplicate of upstream bug
>
Control: tag -1 wontfix
To get any progress with this issue, please collaborate with upstream.
>
> Hello!
>
> I can see in the logs:
>
> 2017-11-06 17:10:13 139930521723456 [Warning] WSREP: access
> file(/var/lib/mysql//gvwstate.dat) failed(No such file or directory)
>
> This issue might
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!
su 6. tammik. 2019 klo 23.52 Nikolay Dimitrov
(nikolay.dimit...@retrohub.org) kirjoitti:
>
> Hi Otto, Helmut,
>
> Thanks for fixing the bug and sharing the progress with me.
>
> To be honest, I could have sent a patch for this issue even back then,
> but I'm not familiar with Debian's
ap=UTF-8) (ignored:
> LC_ALL set to en_US.UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages libmariadbclient-dev-compat depends on:
> ii libmariadbclient-dev 10.1.26-0+deb9u1
>
> libmariadbclient-dev-compat reco
Hello!
su 6. tammik. 2019 klo 12.54 Helmut Grohne (hel...@subdivi.de) kirjoitti:
>
> Hi Otto,
>
> On Sun, Jan 06, 2019 at 12:19:50PM +0200, Otto Kekäläinen wrote:
> > Currenlty in Debian unstable we have mariadb-10.3. Would you be kind
> > and rebase, test and submit yo
Hello Helmut!
su 6. tammik. 2019 klo 12.09 Helmut Grohne (hel...@subdivi.de) kirjoitti:
>
> Control: tags -1 + patch
>
> On Fri, Oct 13, 2017 at 01:47:19AM +0300, Nikolay Dimitrov wrote:
> > Can you please double-check whether mysqlclient.pc is installed at the
> > proper path?
>
> It isn't.
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:
>
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
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
Package: mariadb-plugin-mroonga
Version: 10.3.11-1
Severity: normal
Tags: newcomer
The postinst of Mroong install is, and the postrm uninstalls it
correctly. There is however no code that would on a
postinst/preinst/upgrade scenario reinstall the plugin if the path has
changed (eg. as it does on
Package: mariadb-plugin-spider
Version: 10.3.11-1
Severity: normal
Tags: newcomer
The postinst of Spider installs the plugin automatically:
*
mariadb-10.3/debian$ cat mariadb-plugin-spider.postinst
#!/bin/sh
set -e
Olaf van der Spek kirjoitti su 30. joulukuuta 2018 klo
14.24:
> On Sun, Dec 30, 2018 at 1:21 PM Otto Kekäläinen wrote:
> >
> > Package: mariadb-10.3
> > Version: 10.3.11-1
> > Severity: normal
> > Tags: newcomer
> >
> >
> > The new MariaDB 10.3
Package: mariadb-10.3
Version: 10.3.11-1
Severity: normal
Tags: newcomer
The new MariaDB 10.3 has it's library so version upgraded from 18 to 19.
This means that the plugin files will also reside in another directory. If
any of the plugins were active before the upgrade, they may fail to load
Control: tags -1 moreinfo
Hello Jörg!
This bug (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876398)
seems to be due the fact that the mysqltest binary does not support
this option. It supports character_set but not default_character_set.
I don't know what the solution would be here. Maybe
Hello!
pe 15. syysk. 2017 klo 19.18 Guido Günther (a...@sigxcpu.org) kirjoitti:
> Hi,
> it would be great if the package would ship upstream's profile (even if
> only in complain mode like upstream does). This would help to iron out
> the issues in the profile.
The problem is that we don't have
Control: tags -1 moreinfo
Hello Albert!
Is this issue already resolved for you?
Maintaining MariaDB in Debian requires a lot of work and if you find
this package important for you, please contribute by helping fix this
bug. Also, if you test out current MariaDB 10.3 in Debian and find any
new
Hello!
ma 24. jouluk. 2018 klo 13.58 Olaf van der Spek (olafvds...@gmail.com)
kirjoitti:
>
> Op ma 24 dec. 2018 om 12:49 schreef Olaf van der Spek :
> >
> > Op ma 24 dec. 2018 om 12:38 schreef Otto Kekäläinen :
> > >
> > > Tags: wontfix
> > &g
Control: tags -1 moreinfo
Hello!
What does 'find /etc/mysql -ls' show for you?
Maybe the original problem is that you edited the wrong configuration
file and it was lost on upgrade?
Due how mysql-common works in Debian, the /etc/mysql/my.cnf is not a
real file but a symlink to the real config,
Control: tags -1 moreinfo
Hello!
This issue is still open, as is the upstream issue
https://jira.mariadb.org/projects/CONC/issues/CONC-211
I would be happy to review some proof-of-concept how you would
implement this if you can.
Maintaining MariaDB in Debian requires a lot of work and if you
Control: tags -1 moreinfo
The packaging of 10.3.0 last year was very experimental by nature
indeed. Now it is properly packaged and also mysql-defaults is
updated.
Can you still reproduce this issue?
Maintaining MariaDB in Debian is a very big task and I appreciate all
help I get that
Control: tags -1 moreinfo
Hello!
The file mariadb.cnf is shipped from mariadb-common package and it
should be found on every machine where MariaDB is installed.
You probably had some customization or 3rd party packages installed.
Please investigate it yourself what customization you had.
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
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.
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
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
Hello!
to 27. jouluk. 2018 klo 16.19 Helge Deller (del...@gmx.de) kirjoitti:
> Yes, I presented two possibilities how *I believe* this bug can get fixed:
> a) Add it to the list of unstable platforms where the test results should be
> ignored, or
> b) Add a unstable-tests.hppa file (it seems
Thanks for submitting a bug report!
Since you seem to know how to potentially fix this, please file a
merge request on Salsa so I can include your fix in the next upload.
Instructions on how to do that can be found at
https://wiki.debian.org/Teams/MySQL/patches
It should be quite easy and we have
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
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
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
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
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)?
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
.
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
Tags: wontfix
The dependency was set to Recommends in
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/da407b9f50a13c0ee69709156b82e6ddb43065e0
to avoid circular rependencies, as libdbd-mysql-perl itself depends on
the MySQL client library.
I am however leaving this bug report open in
The options innodb_file_format and innodb_large_prefix no longer exist
in 10.3, so they need to be removed.
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/ae10a7fca8ddbc4f448f6a106440e9d8cbe14eac
Apparenlty we need something else to allow large keys again?
Hello John!
Do you have any estimate when you could finalize the patch, so it can be
included in the next upload?
John Paul Adrian Glaubitz kirjoitti pe 21.
joulukuuta 2018 klo 19.20:
> Hello!
>
> On 12/16/18 10:37 PM, John Paul Adrian Glaubitz wrote:
> > That's odd. I rebased it against the
Hello!
pe 21. jouluk. 2018 klo 19.20 John Paul Adrian Glaubitz
(glaub...@physik.fu-berlin.de) kirjoitti:
>
> Hello!
>
> On 12/16/18 10:37 PM, John Paul Adrian Glaubitz wrote:
> > That's odd. I rebased it against the latest mariadb-10.3 package in
> > experimental, i.e. version 1:10.3.11-1~exp1.
>
> 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
>
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
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
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
su 16. jouluk. 2018 klo 22.10 John Paul Adrian Glaubitz
(glaub...@physik.fu-berlin.de) kirjoitti:
>
> On 12/16/18 9:04 PM, Otto Kekäläinen wrote:
> > Can you please provide a link to where you upstreamed it?
>
> It's in the "Forwarded" field of this bug report. I
> Attaching an updated version of the patch.
>
> Please note, without the patch, mariadb-10.3 will not build on mips32 and
> several other 32-bit platforms.
Thanks!
Can you please provide a link to where you upstreamed it?
We already have 21 patches and maintaining them year after year has
its
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?
Also note these issues where upstream has tweaked how symbols are
published and versioned:
* https://jira.mariadb.org/browse/MDEV-13619
*
Hello!
Thanks for the report. Can you reproduce this with latest libmariadb3
package? The old libmariadb2 series is not maintained in Debian
anymore.
Hello!
This change was done by Ondrej Sury. I don't have any more information
about it other than what the commit messages say.
My last email was a false positive, I looked at the wrong patch. Your patch
was fine.
Release 1:10.1.37-2 was just uploaded and you should be able to verify that
all builds are OK within a few days.
Hello Samuel!
While running "quilt push" I noticed the patch does apply cleanly:
Now at patch hurd.patch
Warning: trailing whitespace in lines 3,15 of cmake/os/GNU.cmake
Patch hurd.patch is unchanged
Applying patch fix-mips-compilation-failure-__bss_start-symbol-miss.patch
(Stripping trailing
ma 5. marrask. 2018 klo 1.26 Samuel Thibault (sthiba...@debian.org) kirjoitti:
>
> Otto Kekäläinen, le lun. 05 nov. 2018 00:46:18 +0200, a ecrit:
> > Sorry, I just realized the gitlab-ci.yml for server was not merged on
> > master yet. I will fix that within 24 hours (nee
ma 5. marrask. 2018 klo 0.33 Samuel Thibault (sthiba...@debian.org) kirjoitti:
>
> Otto Kekäläinen, le dim. 04 nov. 2018 23:04:23 +0200, a ecrit:
> > I would appreciate it a lot if you can submit them as Merge Requests
> > on Salsa and have the debian/gitlab-ci.yml featu
Hello!
Thanks for the patches!
I would appreciate it a lot if you can submit them as Merge Requests
on Salsa and have the debian/gitlab-ci.yml feature enabled on your
commits:
https://wiki.debian.org/Teams/MySQL/patches
Thanks Samuel!
su 4. marrask. 2018 klo 14.18 Samuel Thibault (sthiba...@debian.org)
kirjoitti:
> Hello,
>
> Otto Kekäläinen, le lun. 15 oct. 2018 12:02:46 +0300, a ecrit:
> > Since upstream is positive, please make a PR directly on upstream at
> > https://github.com/cod
Hello!
I would be happy to get merge requests on documentation improvements or
even default path code changes at
https://salsa.debian.org/mariadb-team/mariadb-connector-c
I promise to review and merge them quickly if you contribute. Thanks!
Otto
Hello!
Thanks for the report and patch.
Can you please report this upstream and get their opinion on this?
Or even make a pull request on https://github.com/codership/galera/issues ?
This package follows upstream very carefully and we don't have any
Debian-only patches around at the moment. If
Hello!
I can see in the logs:
2017-11-06 17:10:13 139930521723456 [Warning] WSREP: access
file(/var/lib/mysql//gvwstate.dat) failed(No such file or directory)
This issue might ultimately be related to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874025
or upstream
any logic, just deals
> with differences in ifreq struct member naming between different
> OS/kernel implementations.
>
> - Teemu
>
> On 2018-08-14 11:49, Otto Kekäläinen wrote:
> > Hello!
> >
> > Patch received in Debian. What do you think about it?
> >
&g
Hello!
Thanks for the report and patch.
Can you please report this upstream and get their opinion on this?
Or even make a pull request on https://github.com/codership/galera/issues ?
This package follows upstream very carefully and we don't have any
Debian-only patches around at the moment. If
Forwarded: https://github.com/codership/galera/issues/313
Hello!
This looks like a duplicate of upstream bug
https://github.com/codership/galera/issues/313
This is not something we should fix on packaging level in Debian.
Please contribute upstream to get this fixed once and for all.
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
Package: mariadb-10.1
Severity: wishlist
Go through all configs we have, and try to make them smaller. Ideally
we would not have any settings ourselves, but use all defaults as
upstream ships them.
First step is at least read all options we set in the default config
files, and check what their
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!
su 30. huhtik. 2017 klo 21.06 Laurent Bigonville (bi...@debian.org) kirjoitti:
> Shouldn't mariadb be built with numa support?
Upstream MariaDB 10.1 does not seem to build with numa. However 10.3
is doing so, and we will soon import 10.3 into Debian, and then build
it with libnuma as
Control: tags -1 moreinfo
Hello Joe!
Can you please confirm if this is fixed for you now so we can close this issue?
ke 25. heinäk. 2018 klo 16.12 Otto Kekäläinen (o...@debian.org) kirjoitti:
>
> Hello!
>
> The package libmariadb-dev contains the client library files.
>
Control: tags -1 moreinfo
Hello!
You have used an version from experimental that was badly packaged and
not intended for wider use.
Can you please confirm if this issue is present in the latest
libmariadb3 et al in Debian sid?
ke 21. helmik. 2018 klo 15.57 Takuro Ashie (as...@clear-code.com)
Control: tags -1 moreinfo
Hello Aaron!
su 4. maalisk. 2018 klo 7.24 Otto Kekäläinen (o...@debian.org) kirjoitti:
>
> Current Debian packaging now has:
>
> mariadb-connector-c$ head debian/libmariadb3.symbols
> libmariadb.so.3 libmariadb3 #MINVER#
> libmariadb_3@
Control: merge -1 868131
This is a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868131 and will be
fixed in 3.0.6-1.
Control: tags -1 wontfix
Hello!
The whole point of a -compat package is that it replaces the other
with files with the same names in the same paths.
You cannot co-install them and there should be no need or use case for
anybody to want to do so. Use either one.
$ sudo apt install
Control: tags -1 moreinfo
Hello!
You have used an version from experimental that was badly packaged and
not intended for wider use.
Can you please confirm if this issue is present in the latest
libmariadb3 et al in Debian sid?
ke 21. helmik. 2018 klo 15.33 Takuro Ashie (as...@clear-code.com)
Control: tags -1 -patch
> Solution (should work for stretch release cycle and probably beyond):
>
> Firstly, the db_critical input should be a boolean question
> (defaulting to false) rather than a note (and it should perhaps
> mention /etc/mysql/debian.cnf as well, but I'm not sure about that),
Control: tags -1 help wontfix
Just for the record, the MariaDB installed by Debian is secure by
default. There is no need to run mysql_secure_installation. You should
only use that binary if you also used mysql_install_db etc manually to
setup the database.
So, just run 'sudo apt install
Control: tags -1 moreinfo
This is related to the upstream code that does in-place binary upgrade
or similar. This is nothing we can fix in the packaging I suspect, but
should be reported upstream.
Also we more information would be needed on how to reproduce this
issue. It cannot be fixed unless
This is how the mysqld outputs things. I don't know why, there might
be some special reason to this odd behavious.
An issue about this should be reported upstream. It is nothing we can
fix in the packaging in Debian.
Control: retitle -1 "mariadb install fails with NO_NEW_PRIVILEGES (systemd)"
Thanks for reporting this. The systemd issues are tricky to reproduce
let alone to fix. At the moment I have no clue what to change in the
packaging to mitigate the issue reported in this bug report.
Control: merge -1 886756
This seems to be a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886756
Control: tags -1 moreinfo
Anybody else experiencing this?
Faustin, are you able to reproduce it? Any upstream MDEVs about this?
This is due to the system having a previos AppArmor profile, that is
still enforced.
I don't know if it can be fixed. Maybe the preinstall script should
deactivate the profile?
AppArmor causes a lot of weird errors when it stops the mysqld from
working as expected, and the code inside mysqld
Control: tags -1 moreinfo
What are the settings of your /etc/mysql directory? ls -la ?
Do you have AppArmor enabled?
With this report we cannot know what is preventing mysqld from reading
your config.
Control: tags -1 +moreinfo
James, can you please check if upstream applied the patch correctly
and this issue can be closed, or if you think something additional
still needs to be patched downstream here in Debian?
- Otto
Tags: -patch moreinfo
Thank you Chris for updating the translation! Please re-send it.
However it seems the attached patch is a translation of xz, not
MariaDB 10.1 at all.
tags - patch + moreinfo
It seems the attached patch is a translation of xz, not MariaDB 10.1 at all.
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
Hello!
The package libmariadb-dev contains the client library files.
Use the package libmariadbd-dev for server stuff.
Yes, package names are very close to each other, but this is the same
naming scheme as in mysql vs mysqld.
- Otto
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.
>From upstream developer Sergei Petrunia:
"fix-FTBFS-on-GNU-Hurd.patch - adjusted and applied (patch-to-that
patch, fix for debian bug# 882062 is applied as well)"
Source: https://jira.mariadb.org/browse/MDEV-14900#comment-113248
That Jira instance is not integrated with Github, so I cannot
901 - 1000 of 1440 matches
Mail list logo
