Bug#845295: [debian-mysql] Bug#845295: mariadb-server-10.0: timeout at startup

Hello! I've implemented systemd in Debian in https://anonscm.debian.org/git/pkg-mysql/mariadb-10.1.git/commit/?id=9ff0a57dcbce86031d654dd85edd5bfe8c795dfa based on the scripts shipped by upstream. Could you review it? And help test is works as expected and also fixes this timeout issue? Test

Bug#835596: [debian-mysql] Bug#835596: Bug#835596: [mariadb-10.0] Please ship support-files/mysqld_multi.server.sh

Hello Jan! I've implemented systemd in Debian in https://anonscm.debian.org/git/pkg-mysql/mariadb-10.1.git/commit/?id=9ff0a57dcbce86031d654dd85edd5bfe8c795dfa based on the scripts shipped by upstream. It also contains a mariadb@.service intended for the multi mysqld use case. Read more at:

Bug#852267: [debian-mysql] Bug#852267: upgrading mariadb-server-10.0 to mariadb-server-10.1 removed it instead of upgrading

2017-01-23 19:09 GMT+02:00 Jean-Marc : > I'll try to simulate it by installing dolibarr on a Debian Jessie and > upgrading it to testing. > > I'll keep you posted. Thanks for your help! I cannot possibly test all the upgrade scenarios people might have out there, so it is very

Bug#851195: [debian-mysql] Bug#851195: Bug#851195: Bug#851195: mariadb-server-10.1: Time Zone system tables are empty

I tested this with the upstream version too: Server version: 10.1.21-MariaDB-1~sid mariadb.org binary distribution Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB

Bug#851132: [debian-mysql] Bug#851132: /usr/sbin/mysqld: ssl_ciphers not working; mariadb built without TLS support?

Ok, this is now figured out. To activate YaSSL you must have 'ssl=on' in the config and no ssl_cipher defined. 50-server.cnf: ssl=on => MariaDB [(none)]> SHOW VARIABLES LIKE '%ssl%'; +-+-+ | Variable_name | Value |

Bug#852495: [debian-mysql] Bug#852495: mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links

Tags: unreproducible 2017-01-25 0:21 GMT+02:00 Julian Gilbey : > After upgrading to 10.1 from 10.0, I purged the old > mariadb-server-10.0 package, but this had two quite unpleasant > effects: it shut down the server and it removed the init.d links. > This is because: I was not

Bug#808420: [debian-mysql] Bug#808420: Implemented systemd scripts for MariaDB

2017-01-24 17:05 GMT+02:00 Johannes Kliemann : > I have tested it and it works good for me. > It only seems there is no reload job for systemd. Is this intended? Thanks! It seems there is no reload support. We are now using the upstream systemd script, and to keep maintenance

Bug#852709: [debian-mysql] Bug#852709: Patch

Great work Dieter! I'll merge and upload immediately. I just hope this will be in time before the Feb 5th freeze... Because the unstable->testing counter resets on every upload, all old fixes are still pending +10 days after this upload.

Bug#853137: [debian-mysql] Bug#853137: mariadb-server-10.1: Installation hangs, "InnoDB: Unable to lock ./ibdata1, error: 11"

2017-01-30 14:06 GMT+02:00 Philipp Marek : >> > > InnoDB: Check that you do not already have another mysqld process using >> > > the same InnoDB data or log files. >> > >> > Did you? >> > >> > What does 'ps fax | grep mysql' yield? > # ps fax | grep maria >

Bug#853137: [debian-mysql] Bug#853137: mariadb-server-10.1: Installation hangs, "InnoDB: Unable to lock ./ibdata1, error: 11"

2017-01-30 9:25 GMT+02:00 Philipp Marek : > InnoDB: Check that you do not already have another mysqld process using the > same InnoDB data or log files. Did you? What does 'ps fax | grep mysql' yield?

Bug#851132: [debian-mysql] Bug#851132: /usr/sbin/mysqld: ssl_ciphers not working; mariadb built without TLS support?

2017-01-25 12:10 GMT+02:00 Matthew Sackman <matt...@wellquite.org>: > On Wed, Jan 25, 2017 at 09:44:00AM +0200, Otto Kekäläinen wrote: >> Ok, this is now figured out. >> >> To activate YaSSL you must have 'ssl=on' in the config and no >> ssl_cipher defined.

Bug#852495: [debian-mysql] Bug#852495: Bug#852495: mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links

Hello! I tested the scenario where a system had mariadb-server-10.0 et al installed in Jessie, and then upgrades to Stretch. In Streatch mariadb-server-10.0 is replaced by 10.1 but not purged. Then I ran $ apt-get purge mariadb-*-10.0 The following packages will be REMOVED:

Bug#851975: [debian-mysql] Bug#851975: mariadb-connector-c: FTBFS on mips, s390x (and all other big-endian architechtures?)

I filed this regression upstream earlier today: https://jira.mariadb.org/browse/CONC-226

Bug#852728: [debian-mysql] Bug#852728: FTBFS on non-Linux architectures

The apply errors where: $ git apply 0001-Fix-FTBFS-on-non-Linux-architectures.patch 0001-Fix-FTBFS-on-non-Linux-architectures.patch:18: trailing whitespace. #!/usr/bin/dh-exec 0001-Fix-FTBFS-on-non-Linux-architectures.patch:27: trailing whitespace. [linux-any]

Bug#832931: (no subject)

Please also note the related https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852728 and PR at https://github.com/ottok/mariadb-10.1/pull/8

Bug#832931: (no subject)

2017-01-27 9:18 GMT+02:00 Otto Kekäläinen <o...@seravo.fi>: > Please also note the related > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852728 and PR at > https://github.com/ottok/mariadb-10.1/pull/8 Actually Bug#852728 has nothing to do with this, my mistake. But the PR i

Bug#852495: [debian-mysql] Bug#852495: Bug#852495: Bug#852495: mariadb-server-10.[01]: purging old mariadb-server shuts down mariadb-server and removes init.d links

Thanks Julian, you've done a very thorough job in producing and documenting the patch. In future, if you send a patch, please do it as public git branches so I can easily pull (and you can easily rebase when the target repo updates). Or alternatively you can send patches on Github as pull

Bug#852621: [debian-mysql] Bug#852621: libmariadbclient-dev: lintian error: pkg-config-multi-arch-wrong-dir

Hello Julian! Thanks for contributing to the packaging of MariaDB 10.1 in Debian. The Lintian error has been there for a while and no override has been added, because it is indeed an actual issue that should be fixed. However, fixing it is not that easy, so it hasn't been done yet. Do you think

Bug#852776: [debian-mysql] Bug#852776: mariadb-server-10.1: init script doesn't specify it should be started prior to apache2 etc

Affects: mysql-5.7 Hello! Thanks for the report. The same lines are also in https://anonscm.debian.org/git/pkg-mysql/mysql.git/tree/debian/rules#n215 Git history shows the line is inherited way back from 5.5 times. As MariaDB and MySQL and functionally equvalent, we try to keep their packaging

Bug#852728: [debian-mysql] Bug#852728:

Fixed already in https://github.com/ottok/mariadb-10.1/pull/6 I will upload ASAP when possible. Some other changes may come in today too.

Bug#852728: [debian-mysql] Bug#852728: FTBFS on non-Linux architectures

Thanks for the patch! It did though include whitespace characters etc so I had to apply it manually. In the future I'd prefer to get patches as public git branches I can easily pull (and you can easily rebase when the target repo updates). Or alternatively you can send patches on Github as pull

Bug#852709: [debian-mysql] Bug#852709: Patch

2017-01-29 17:12 GMT+02:00 James Clarke : > Yeah, I'm not sure what's wrong with your setup. I would suggest checking the > version of dpkg-dev inside your chroot, since that should be the only thing > determining whether the package is built. Does the build log show it building

Bug#852709: [debian-mysql] Bug#852709: Patch

Hello! 2017-01-28 3:32 GMT+02:00 James Clarke : > Are you using a very old chroot? You need dpkg-dev (>= 1.18.11) to support > quadruplets in the Architecture field, though that was uploaded on the 6th > November... No TokuDB in unstable now:

Bug#855098: mariadb-server: Passwordless root access does not work on new installation

Hello! There is a Debian.README, you did find it and you are using the correct commands. It just does not work. You don't seem to have a fresh install, but you have upgraded from something special or you have a customized mysql.user table.

Bug#855163: [debian-mysql] Bug#855163: Missing mariadb-plugin-tokudb binary package on amd64

So you suggest I upload 10.1.21-6 and go though all the hassle of filing unblocks etc? Is there no possibility to trigger a rebuild on amd64 with the current source package?

Bug#855163: [debian-mysql] Bug#855163: Missing mariadb-plugin-tokudb binary package on amd64

2017-02-14 23:58 GMT+02:00 James Clarke <jrt...@debian.org>: >> On 14 Feb 2017, at 21:54, Otto Kekäläinen <o...@debian.org> wrote: >> >> So you suggest I upload 10.1.21-6 and go though all the hassle of >> filing unblocks etc? Is there no possibil

Bug#808420: [debian-mysql] Bug#808420: Implemented systemd scripts for MariaDB

Hello Johannes! I've implemented systemd in Debian in https://anonscm.debian.org/git/pkg-mysql/mariadb-10.1.git/commit/?id=9ff0a57dcbce86031d654dd85edd5bfe8c795dfa based on the scripts shipped by upstream. Could you review it? And help test is works as expected? Test binaries available via repo

Bug#851195: [debian-mysql] Bug#851195: Bug#851195: mariadb-server-10.1: Time Zone system tables are empty

Hello! Your patch was committed in https://anonscm.debian.org/gitweb/?p=pkg-mysql/mariadb-10.1.git;a=commit;h=c840b371166afd05b96a94e2056bf8c65a5a8589 In addition to the official git.debian.org mariadb-10.1 repository there is also a Github mirror if you are able to produce a patch and want to

Bug#851132: [debian-mysql] Bug#851132: Bug#851132: /usr/sbin/mysqld: ssl_ciphers not working; mariadb built without TLS support?

For the record, I also tested this on Ubuntu Yakkety with the version 10.0.28-0ubuntu0.16.10.1 and I get the same warning in syslog: mysqld: 170119 9:47:47 [Warning] Failed to setup SSL mysqld: 170119 9:47:47 [Warning] SSL error: Failed to set ciphers to use It seems something with how we do "

Bug#487461: Default charset

MariaDB in Debian has had utf8mb4 as the default charset for more than a year now. Maybe we could close this issue as fixed? https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.1.git/commit/?id=e6ade2be57856736e8bc8039d71b35f9ffcde48e

Bug#850216: [debian-mysql] Bug#850216: Bug#850216: Bug#850216: mysql-server-5.6: Listens on * by default after installation (related to use of alternatives)

to this new config scheme should be placed in /etc/mysql/mariadb.cnf.d/, and for them to be read, mariadb-common must control the configure-symlinks. Maybe we should mark both the client and server packages to conflict each other, and for mariadb-common to conflict on mysql-client and mysql-server?

Bug#851687: [debian-mysql] Bug#851687: mariadb-server-10.1 uninstallable on kFreeBSD and hurd

Yes, here was the complaint regarding depending on iproute: https://jira.mariadb.org/browse/MDEV-10126

Bug#851687: [debian-mysql] Bug#851687: mariadb-server-10.1 uninstallable on kFreeBSD and hurd

Somebody complained to me about using age old iproute, so I updated it in https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.1.git/commit/?id=4d96f3c7be53afe605b3f5d1b03ba6a28c805e82 What is your suggestion on how to solve this? Downgrade back? What shall be done with lsof then?

Bug#851687: [debian-mysql] Bug#851687: mariadb-server-10.1 uninstallable on kFreeBSD and hurd

Many of the new dependencies are related to MariaDB 10.1 including Galera by default. Very good if you can track where exactly they are used as suggest how we lax the dependency without introducing regressions. In addition to the official git.debian.org mariadb-10.1 repository there is also a

Bug#851132: [debian-mysql] Bug#851132: /usr/sbin/mysqld: ssl_ciphers not working; mariadb built without TLS support?

2017-01-15 11:49 GMT+02:00 Matthew Sackman : > Hello, > > Thank you for your reply. I have read through the links you provided, > though I'm afraid I'm still unable to fix this. > > I have ssl-ciphers set in my config, and I have even modified the init > script so that --ssl

Bug#851643: Add postinst/prerm scripts for mariadb-plugin-cracklib

Package: mariadb-10.1 Severity: wishlist Just like other plugins have maintainer scripts that activate/deactivate the plugins automatically upon install, this plugin should also have them. Research what are the correct commands to activate the plugin and implement them in a postinst script. Also

Bug#851644: Add postinst/prerm scripts for mariadb-plugin-gssapi-client/server

Package: mariadb-10.1 Severity: wishlist Just like other plugins have maintainer scripts that activate/deactivate the plugins automatically upon install, this plugin should also have them. Research what are the correct commands to activate the plugin and implement them in a postinst script. Also

Bug#851195: [debian-mysql] Bug#851195: mariadb-server-10.1: Time Zone system tables are empty

I tried multiple variations but the step always fails and looking at /var/log/syslog and /var/log/mysql/error.log I don't understand why. # Add 'set -x' to /var/lib/dpkg/info/mariadb-server-10.1.postinst $ apt-get install -f ... + password_column_fix_query='USE mysql; SET sql_log_bin=0; ALTER

Bug#851195: [debian-mysql] Bug#851195: Bug#851195: mariadb-server-10.1: Time Zone system tables are empty

Hello! 2017-01-20 13:18 GMT+02:00 Daniel Lewart : > (echo "USE mysql;"; mysql_tzinfo_to_sql /usr/share/zoneinfo > 2>/dev/null) | $MYSQL_BOOTSTRAP 2>&1 | $ERR_LOGGER I tried multiple different variants but not exactly the one above. Can you try and send me a patch that is

Bug#832931: mariadb-10.0: FTBFS on powerpc

Hello! I don't understand this fully. The build overview at https://buildd.debian.org/status/logs.php?pkg=mariadb-10.0=powerpc shows 10.0.26 building mostly fine for powerpc. Can you trigger a rebuild to see if it was sporadic? Anyway, I have forwarded this to upstream developers.

Bug#850216: mysql-server-5.6: Listens on * by default after installation (related to use of alternatives)

Hello! 2017-02-23 16:27 GMT+02:00 Robie Basak : > The rule would be: any package that arranges a /etc/mysql/my.cnf > symlink, usually via /usr/share/mysql-common/configure-symlinks, MUST > Provide and Conflict mysql-my-cnf, with the exception of mysql-common. Sorry for

Bug#832931: mariadb-10.0: FTBFS on powerpc

The MariaDB 10.0.26 PowerPC build failure regression was identified and fixed in commit https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=de356c12d3ff73a20e65d1cd7756f3370208ccb2 This has been fixed also upstream and the new 10.0.27 should build OK on PowerPC. Now we just need

Bug#832931: mariadb-10.0: FTBFS on powerpc

release. Can you please point me to the page that lists the exact deadline for next point release? I have a too much work currently and cannot upload .27 immediately. The page https://wiki.debian.org/DebianJessie only lists past point release dates. -- Otto Kekäläinen https://keybase.io/ott

Bug#837300: jessie-pu: package mariadb-10.0/10.0.27-0+deb8u1

Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu The powerpc build of the security release 10.0.26-0+deb8u1 fails to build due to an upstream regression (see Bug#832931). This has been fixed in 10.0.27, but as it is not a security

Bug#809022: [debian-mysql] Bug#809022: Bug#809022: autopkgtest patch for MariaDB

included Elena and Vicentiu as CC: can you comment please? Was there some change in 10.0.27 related to this which might have caused it to behave differently than in .26? 2016-09-09 16:11 GMT+03:00 Kristian Nielsen <kniel...@knielsen-hq.org>: > Otto Kekäläinen <o...@debian.org>

Bug#809022: [debian-mysql] Bug#809022: autopkgtest patch for MariaDB

I uploaded now 10.0.27 and even with the recent fixes, it is still failing. I don't know how to fix it. Can you Paul help debug it? https://ci.debian.net/data/packages/unstable/amd64/m/mariadb-10.0/20160909_103759.autopkgtest.log.gz Setting up mariadb-test-data (10.0.27-1) ... Setting up

Bug#809022: [debian-mysql] Bug#809022: Bug#809022: autopkgtest patch for MariaDB

2016-09-09 23:04 GMT+03:00 Kristian Nielsen : > ci.debian.net, maybe the docs have something, I can try looking. How is this > configured, is everything in the debian packaging, read by autopkgtest? I am not an expert on autopkgtest. This was implemented by Paul Gevers

Bug#809022: [debian-mysql] Bug#809022: Bug#809022: Bug#809022: autopkgtest patch for MariaDB

2016-09-10 19:04 GMT+03:00 Kristian Nielsen : > Otto, so this problem will be solved with the next upstream release > (assuming my understanding is correct, but Paul's analysis seemed very > plausible). And if you want the ci.debian.net failures fixed before then, > you

Bug#837300: jessie-pu: package mariadb-10.0/10.0.27-0+deb8u1

2016-09-12 15:16 GMT+03:00 Adam D. Barratt <a...@adam-barratt.org.uk>: > On 2016-09-11 14:41, Adam D. Barratt wrote: >> >> On Sat, 2016-09-10 at 14:42 +0300, Otto Kekäläinen wrote: >>> >>> The powerpc build of the security release 10.0.26-0+deb8u1 fails to

Bug#831844: [debian-mysql] Bug#831844: mysql-5.6: Multiple security fixes from the July 2016 CPU

Hello! 2016-09-22 18:10 GMT+03:00 Dominic Hargreaves : > > As I need to have a MySQL 5.6 backport supported for the foreseeable > future, I intend to NMU a new upstream release in the next few weeks. > > Does anyone have any objections to this? I've accepted your Alioth join

Bug#702280: libdbd-mysql-perl / mariadb update

Hello! 2016-09-24 19:29 GMT+03:00 gregor herrmann : > What I'd like to see is > - a confirmation that this is indeed the final decision, since there > was a discussion round default-libmysqlient-dev on -devel after the > announcement; Yes, this is the setup we have agreed

Bug#838603: Lintian: Extend obsolete-packages with the mysql-* -> default-mysql-* transition

Package: lintian Severity: normal Tags: patch Because of https://lists.debian.org/debian-devel-announce/2016/09/msg0.html I have created a new Lintian rule that helps maintainers to remember to use virtual-mysql-* packages instead of direct dependencies. After discussion with Niels Thykier I

Bug#838603: Acknowledgement (Lintian: Extend obsolete-packages with the mysql-* -> default-mysql-* transition)

I also created an alternative implementation: * https://github.com/ottok/lintian/commit/a5dad829d31ffa565798b895b5a2bcddfba10abc * formatted: https://github.com/ottok/lintian/commit/a5dad829d31ffa565798b895b5a2bcddfba10abc.patch Passed on https://travis-ci.org/ottok/lintian/builds/162106794

Bug#838557: mariadb-10.0: FTBFS on mips64el

could probably be generalized to > other arches, but I didn't want to break anything. > > Thanks, > James -- Otto Kekäläinen https://keybase.io/ottok Seravo Oy and MariaDB Foundation

Bug#838914: mariadb-10.0: testsuite failures on mips/mipsel

That failure seemed to reproduce only on Launchpad. On my local build everything passed OK, including this: plugins.fulltext_plugin [ pass ] 8 plugins.show_all_plugins [ pass ] 21 plugins.sql_error_log[ pass ] 4

Bug#835596: [debian-mysql] Bug#835596: [mariadb-10.0] Please ship support-files/mysqld_multi.server.sh

Hello! Sorry for not replying to this earlier. You description seems accurate and idea good. It would be great if you can provide a patch or a PR and I'lll merge it quickly.

Bug#838914: mariadb-10.0: testsuite failures on mips/mipsel

Hello! Thank you very much and well done for fixing so many test failures in one go! I noticed however that one test started to fail om amd64 now. Builds on i386 and ppc64 are OK. Output below and full log visible at

Bug#809022: [debian-mysql] Bug#809022: Bug#809022: autopkgtest patch for MariaDB

For the record, it is now confirmed that autopkg-test finally works: https://ci.debian.net/packages/m/mariadb-10.0/unstable/amd64/ => 10.0.27-2 2016-10-03 21:26:20 UTC 0h 11m 30s pass Thanks Kristian and Paul!

Bug#828306: [debian-mysql] Bug#828306: Bug#828306: galera-3: FTBFS with openssl 1.1.0

You increased the seriousness of this issue, with the result of upcoming autoremoval of galera-3 from Debian testing despite OpenSSL 1.1 not being available in testing yet, and not even in unstable yet. Galera-3 currently builds fine in testing and unstable. Also the build problem with OpenSSL is

Bug#842454: [debian-mysql] Bug#842454: default-libmysqlclient-dev is unsatisfiable for cross builds

Thank you very much Helmut for this patch! I've committed it in https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=b3eb803a601ffc98aa7fe24b625edcd9ba1031e8 I'll wait for a few days if somebody wants to chip in on something and then upload mysql-defaults 1.0.1 to Debian unstable. PS.

Bug#842505: RM: mariadb-client-lgpl -- ROM; obsoleted by mariadb-connector-c

Package: ftp.debian.org Severity: normal The source package mariadb-client-lgpl was renamed to mariadb-connector-c. At the same time some binary packages were also renamed. To finalize this change, please remove from testing and unstable the following binary packages that have become obsolete:

Bug#842454: [debian-mysql] Bug#842454: default-libmysqlclient-dev is unsatisfiable for cross builds

Hello! 2016-10-30 0:18 GMT+03:00 Helmut Grohne : > The presence of Multi-Arch: same indicates that the package can be > unpacked multiple times for different architectures at the same time. > Their files may overlap if and only if the content is equal for > overlapping files.

Bug#842454: [debian-mysql] Bug#842454: Bug#842454: default-libmysqlclient-dev is unsatisfiable for cross builds

Andreas, Do you agree with Helmut on the patch now with the new arguments presented? I would like to have an ACK from you before I upload a new mysql-defaults.

Bug#832931: mariadb built successfully on powerpc

2016-11-08 11:08 GMT+02:00 Thadeu Lima de Souza Cascardo : > Hey, > > I built mariadb on my powerpc G4, it took a while and I got some OOM > during some of the tests. So those tests failed, but the package got > built anyway. I wonder if a simple rebuild would make it work on

Bug#842454: [debian-mysql] Bug#842454: Bug#842454: default-libmysqlclient-dev is unsatisfiable for cross builds

2016-10-30 1:45 GMT+03:00 Kristian Nielsen : > Clearly, these libmariadb plugins need to have an arch-dependent path. I > suppose they also need a path that includes the major .so version number of > the libmariadbclient. > > Maybe something like this is needed on the

Bug#842505: closed by Scott Kitterman <deb...@kitterman.com> (already not in unstable)

..@kitterman.com> > To: 842505-d...@bugs.debian.org > Cc: > Date: Sat, 05 Nov 2016 00:31:11 -0400 > Subject: already not in unstable > > > -- Edelleenlähetetty viesti -- > From: "Otto Kekäläinen" <o...@debian.org> > To: Debian Bug Track

Bug#843842: Update build dependency to libmariadb-dev in rmysql

Package: rmysql Severity: important The package RMySQL currently has this build dependency: libmariadb-client-lgpl-dev The MariaDB Connector C package has been renamed about 4 months ago. Please update the dependency to libmariadb-dev The dependency on the old package from stops the

Bug#843841: Update build dependency to libmariadb-dev-compat in neko

Package: neko Severity: important The package Neko currently has this build dependency: libmariadb-client-lgpl-dev-compat | libmysqlclient-dev The MariaDB Connector C package has been renamed about 4 months ago. Please update the dependency to libmariadb-dev-compat |

Bug#843844: Potentially missing files from mariadb-10.0 packages

Package: mariadb-10.0 Severity: wishlist I ran the mariadb-10.0 build with option 'dh --list-missing' and got the output below. Are any of the non-installed files perhaps files we should install? If so, in which package? My notes: - example configs are outdated anyway, probably no point

Bug#842505: closed by Scott Kitterman <deb...@kitterman.com> (already not in unstable)

Hello! 2016-11-09 23:58 GMT+02:00 Mattia Rizzolo : > |trying: -mariadb-client-lgpl > |skipped: -mariadb-client-lgpl (6, 13, 19) > |got: 47+0: a-7:i-24:a-4:a-0:a-0:m-0:m-11:m-0:p-0:s-1 > |* arm64: haxe, mercurial-buildpackage, neko, r-cran-rmysql > > > Fix that, then

Bug#842454: [debian-mysql] Bug#842454: Bug#842454: default-libmysqlclient-dev is unsatisfiable for cross builds

I pushed to my github branch two commits that are supposed to solve this: https://github.com/ottok/mariadb-10.0/commit/5aecef81f774e245f60e8c3f70f44190f7473537 https://github.com/ottok/mariadb-10.0/commit/737359acfbc0d4aff43cdde7e4f7a89cb9873275 I'll do some testing and if nobody objects, push

Bug#835596: [debian-mysql] Bug#835596: Bug#835596: [mariadb-10.0] Please ship support-files/mysqld_multi.server.sh

Are you still interested in making a patch to finalize this? 2016-10-01 19:40 GMT+03:00 Otto Kekäläinen <o...@debian.org>: > Hello! > > Sorry for not replying to this earlier. You description seems accurate > and idea good. It would be great if you can provide a patch or a PR

Bug#842696: [debian-mysql] Bug#842696: mariadb-10.0: FTBFS on hurd-i386: no hostpath(), but no socket path limitation

2016-11-11 17:51 GMT+02:00 Samuel Thibault : > Hello, > > Samuel Thibault, on Mon 31 Oct 2016 12:56:53 +0100, wrote: >> mariadb-10.0 FTBFS on hurd-i386: > > Could you consider making an upload soon, now that 10.0.28-1 has > migrated to testing? The issue is blocking litteraly

Bug#845295: [debian-mysql] Bug#845295: mariadb-server-10.0: timeout at startup

Hello! What does the syslog or other logs say, what was the real reason MariaDB failed to start?

Bug#845205: [debian-mysql] Bug#845205: Incompatible with MariaDB 10.1

Hello! Debian contains at the moment MariaDB 10.0. Please don't file bugs against packages that are from 3rd party repos and not from Debian.org. 2016-11-21 14:48 GMT+02:00 Matt Li : > Package: exim4 > Version: 4.88~RC4-2 > X-Debbugs-CC:

Bug#842696: mariadb-10.0: FTBFS on hurd-i386: no hostpath(), but no socket path limitation

Thanks Samuel for these patches! Are you comfortable with git? Would you like to submit this in the form of at git merge/pull request? The repo is at https://anonscm.debian.org/gitweb/?p=pkg-mysql/mariadb-10.0.git and a mirror at https://github.com/ottok/mariadb-10.0 if you like Github. Here is

Bug#842696: mariadb-10.0: FTBFS on hurd-i386: no hostpath(), but no socket path limitation

Thanks! $ git pull http://people.debian.org/~sthibault/tmp/mariadb-10.0 >From http://people.debian.org/~sthibault/tmp/mariadb-10.0 * branchHEAD -> FETCH_HEAD Updating 2b8bea6..4dcdd0e Fast-forward debian/changelog |5 + debian/patches/hurd_socket.patch

Bug#840646: mariadb-10.0: please move mysql_installdb to core package

8gfDT7qoSooWEBCPit9nJNwPx1vfOzVT > PVMDP96WBhKJ6KFfBjUxvd62Y9NGbO8uYNguW4XQatbbifH5r98MIXJxm7lxV+fM > /uLh5TkNweU4/PdUE2UNIo6Hy3P+zU/NhXQR20j3gVUw8uEkPSVtaz8QRg/wwDNC > tU4zB508qUTv2eE7szMQewxxaSUDVukPy5k+U3qDucL4hSb0 > =T7cW > -END PGP SIGNATURE- > -- Otto Kekäläinen https://keybase.io/ottok Seravo Oy and MariaDB Foundation

Bug#840646: [debian-mysql] Bug#840646: mariadb-10.0: please move mysql_installdb to core package

bug. I don't think that is in conflict > with this request at all, but it would probably be worth adding to a > list of rearrangements and Breaks/Replaces to add, then doing everything > at once. Agree -- Otto Kekäläinen https://keybase.io/ottok Seravo Oy and MariaDB Foundation

Bug#840857: [debian-mysql] Bug#840857: mariadb-server: MariaDB 10.1?

We have planned to jump directly to MariaDB 10.2 but it depends on many details. We can track the status in this issue.

Bug#841636: [debian-mysql] Processed: Merge duplicates

Have you tried building with MariaDB Connector C/C++ (package libmariadb-dev) instead of the MySQL Connector C++? 841636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841636 844275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844275 844302:

Bug#830976: logrotate failures if mysql server is not running

Hello! 2016-12-14 15:42 GMT+02:00 Meik Hellmund : > Followup-For: Bug #830976 > > > I got errors from cron: > /etc/cron.daily/logrotate: > logrotate_script: 3: [: /var/run/mysqld/mysqld.pid: unexpected operator > > The reason I found: The postrotate script of

Bug#847750: rmysql: FTBFS on mips64el

ne. Same on mips64el? >> >> Dirk >> >> | * rpm: mariadb-devel | mysql-devel (Fedora, CentOS, RHEL) >> | * csw: mysql56_dev (Solaris) >> | * brew: mariadb-connector-c (OSX) >> | If libmysqlclient is already installed, check that 'pkg-config' is in your &

Bug#848287: [debian-mysql] Fwd: osmalchemy is marked for autoremoval from testing

2017-01-12 23:38 GMT+02:00 Kristian Nielsen : > If I understand the issue here, this is nothing to do with MariaDB being or > not being a drop-in for MySQL. The problem seems to be this patch in the > Debian packaging: > > >

Bug#851132: [debian-mysql] Bug#851132: /usr/sbin/mysqld: ssl_ciphers not working; mariadb built without TLS support?

Hello! Thanks for reporting. MariaDB 10.1 is built with a bundled YaSSL. I don't directly see why you don't see the ciphers. Thanks if you can help with bugging. This issue might also be of interest as it explains why we have YaSSL instead of OpenSSL:

Bug#850147: mariadb-10.0: stretch should be released with mariadb-10.1 only

2017-01-13 0:42 GMT+02:00 Andreas Beckmann : > Looks good. Cloning/reassigning/retitling the bug accordingly, to keep > an RC bug against mariadb-10.0 open. Ok, so we need to have one RC against 10.0 open all the time to prevent it from migrating from unstable to testing until it

Bug#850216: [debian-mysql] Bug#850216: Bug#850216: mysql-server-5.6: Listens on * by default after installation (related to use of alternatives)

Thanks Robie for the analysis. Fixed as suggested in https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.1.git/commit/?id=75fa84af6bdf84ff95bd0cabb2a8966330d77154

Bug#850147: mariadb-10.0: stretch should be released with mariadb-10.1 only

Fix committed in https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/commit/?id=9ead71eaee19f5c701f7e6c7a9919b2c7de6418b

Bug#808420: [debian-mysql] Bug#808420: Implemented systemd scripts for MariaDB

ts.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- Otto Kekäläinen https://keybase.io/ottok Seravo Oy and MariaDB Foundation

Bug#847750: rmysql: FTBFS on mips64el

2016-12-19 1:19 GMT+02:00 Dirk Eddelbuettel : > > On 19 December 2016 at 00:05, Andreas Beckmann wrote: > | I just tried rmysql on the porterbox eller. B-D cannot be installed in > | sid due to a dpkg-maintscript-helper bug, but stretch works fine. > | I could build the package in

Bug#848603: Enable innodb_large_prefix

2016-12-20 3:07 GMT+02:00 Christian Hofstaedtler : > pdns-backend-mysql I suggest you file a bug against this package. It should define a per-database or per-table charset if it depends it to be of a certain kind. The maintainer of that app knows best that the suitable charset

Bug#848616: #848616: mysql_install_db creates unusable root user

I've tested this a bit. The reason why you cannot access as root the default database is that in Debian we now how unix socket authentication enabled by default, and the default account allows 'root' to access mysqld via socket. So running your mysqladmin as sudo works, but that of course defeats

Bug#848914: [debian-mysql] Bug#848914: mysql-server: supply configuration file for command-line arguments

You might find it useful to know that we have support in mariadb-server init.d script for reading /etc/default/mysql

Bug#847750: rmysql: FTBFS on mips64el

2016-12-17 18:05 GMT+02:00 Dirk Eddelbuettel : > I never heard back from you. > > What do you suggest we do to overcome the fact that mips64el does not seem to > have maria-db ? According to https://buildd.debian.org/status/package.php?p=mariadb-connector-c and

Bug#831639: mariadb-server: mysql_install_db in postinst script does not run

Hello! The program 'logger' is part of the bsdutils package, which is an Essential package (=installed on all Debian systems). If your system is missing it, then your system is somehow weirdly installed. This is a very rare corner case, so I'm dropping severity.

Bug#845295: [debian-mysql] Bug#845295: mariadb-server-10.0: timeout at startup

2016-11-22 11:03 GMT+02:00 Marc Dequènes <d...@duckcorp.org>: > On 2016-11-22 16:47, Otto Kekäläinen wrote: > >> What does the syslog or other logs say, what was the real reason >> MariaDB failed to start? > > > Well, I gave you the systemd log, there's the

Bug#829489: [debian-mysql] Bug#829489: mariadb-server-10.0: Fails to stop, package can't be uninstalled/purged

Please note the lines in your log: Jul 3 20:25:07 c6 /etc/mysql/debian-start[20758]: Version check failed. Got the following error when calling the 'mysql' command line client Jul 3 20:25:07 c6 /etc/mysql/debian-start[20758]: ERROR 1698 (28000): Access denied for user

Bug#842895: mariadb-10.0: CVE-2016-6664 CVE-2016-5617

Hello! CVE-2016-6664 (and duplicate CVE-2016-5617) do not gravely affect MariaDB because: "CVE-2016-6664 is NOT exploitable by itself. Shell access must first be obtained through a vulnerability like CVE-2016-6663. Because CVE-2016-6663 has been fixed and is no longer exploitable, we’ve

Bug#843841: Update build dependency to libmariadb-dev-compat in neko

2016-11-10 19:55 GMT+02:00 Gianfranco Costamagna : > Hi Otto, > > > >>Sure, I'll upload mariadb-connector-c to Jessie backports. > > > it is not even in testing this one :) > > I'm talking about the default-libmysqlclient-dev new package (or whatever is > called) I am

Bug#848603: Enable innodb_large_prefix

Severity: normal We live in a world where WordPress sites expect to be able to save emojis in comments :) We have had utf8mb4 as default in Debian and Ubuntu for a many years. You are experiencing a corner case with a single app (which one?).

<    1   2   3   4   5   6   7   8   9   10   >