Bug#753222: [debian-mysql] Bug#753222: mariadb-5.5: FTBFS: logformat.cc:847: undefined reference to `toku_do_assert_fail(char const*, char const*, char const*, int, int)'

Thanks for reporting the issue. James Page reported a similar issue with building 5.5.38 on Sid, log at http://paste.ubuntu.com/7747594/ However I am unable to reproduce either one of these on my own computer or any public build machines I have access to. Successful recent public builds for sid,

Bug#753222: [debian-mysql] Bug#753222: mariadb-5.5: FTBFS: logformat.cc:847: undefined reference to `toku_do_assert_fail(char const*, char const*, char const*, int, int)'

Source: mariadb-5.5 Ok, this issue is now also confirmed at http://buildbot.askmonty.org/buildbot/builders/debpkg-sid where the only difference between builds #26 and #27 is that a 'apt-get upgrade' was run in between in the build environment, so indeed some new package in Debian unstable breaks

Bug#760173: libjudy.so path broken

Package: libjudy-dev Version: 1.0.5-3 Severity: critical Hello! My package MariaDB 10.0 with OQGraph failed to build and while looking into it I noticed that libjudy-dev was the root cause as the libjudy.so file is installed in wrong path. Check out file listing: [..]

Bug#744910: [debian-mysql] Bug#744910: mysql-5.5: Oracle SPU April 2014

MariaDB 5.5.37 has been in upload ready since Friday, but my sponsor isn't available right now and I don't have upload permissions. All builds and test suites pass as seen in logs at http://buildbot.askmonty.org/buildbot/builders/debpkg-sid

Bug#732967: [debian-mysql] Bug#732967: libmariadbclient18: wrong soname

Hello, 2013/12/23 Ansgar Burchardt ans...@debian.org: Package: libmariadbclient18 Version: 5.5.32-1 Severity: serious The soname for libmariadbclient is wrong as lintian notices: package-name-doesnt-match-sonames libmysqlclient18 ldconfig-symlink-missing-for-shlib

Bug#733002: [debian-mysql] Bug#733002: mariadb-5.5: FTBFS w/bison 3.x

2013/12/23 Sascha Kühndel i...@inusasha.de: this is fixed in upstream version 5.5.33 https://mariadb.atlassian.net/browse/MDEV-4902 This is a known issue. I don't recall the details, but it might be that even with .33a there was some issues. I'll look into this again when I update current .32

Bug#733002: [debian-mysql] Bug#733002: mariadb-5.5: FTBFS w/bison 3.x

Thanks for your effort! However I do not intend to fix 5.5.32 anymore but upgrade to .35 which includes an upstream fix. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#759309: [debian-mysql] Bug#759309: Must not Provide: libmysqlclient-dev

2014-08-26 6:08 GMT+03:00 Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com: On Tuesday 26 August 2014 04:01:05 Steve McIntyre wrote: Package: libmariadbclient-dev Version: 5.5.39-1 Severity: grave libmariadbclient-dev currently includes Provides: libmysqlclient-dev but does not

Bug#759309: [debian-mysql] Bug#759309: Bug#759309: Must not Provide: libmysqlclient-dev

Package: libmariadbclient-dev 2014-08-26 15:52 GMT+03:00 Kristian Nielsen kniel...@knielsen-hq.org: But if I understand correctly, now it is possible to install packages libmariadbclient and package libmysqlclient-dev at the same time. So the problem should no longer apply. Yes,

Bug#759309: [debian-mysql] Bug#759309: Bug#759309: Bug#759309: Must not Provide: libmysqlclient-dev

This fix is now also committed to mariadb-10.0 (among lots of other things), see log at http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/log/ Waiting for upload. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#765664: [debian-mysql] Bug#765664: mariadb-5.5: Multiple security fixes from October 2014 CPU could affect MariaDB

MariaDB has now pubished this page that tracks CVE (Oracle issued and others) to MariaDB releases, also post-release: https://mariadb.com/kb/en/mariadb/development/security/ We are in the process of uploading MariaDB 10.0 to unstable very soon, and that will depricate MariaDB 5.5 so I do not plan

Bug#765664: [debian-mysql] Bug#765664: mariadb-5.5: Multiple security fixes from October 2014 CPU could affect MariaDB

2014-10-21 23:53 GMT+03:00 Salvatore Bonaccorso car...@debian.org: Take this as personal point of view so far: So the idea is to get MariaDB 10 into Jessie? Note that the freeze is coming soon and any new ustream version need to be in testing on 5th of november. AFAIR from the last discussion

Bug#769212: [debian-mysql] Bug#769212: mariadb-10.0: FTBFS in jessie: Tests failures

I've analyzed the log and found the issue (test comparison failed due to capitalization issues in the word USER vs user). With the help of upstream a patch has been produced and I've tested it and pushed it in commit

Bug#609537:

Hello! In MariaDB the script has a section that waits for a long time so that even the biggest and busiests databases will have enough time to shut down: for i in `seq 1 600`; do sleep 1 if mysqld_status check_dead nowarn; then server_down=1; break; fi done if

Bug#769865: [debian-mysql] Bug#769865: mariadb-10.0: FTBFS on i386

Just for the record: I have done a test build and ran the test suites, but it seems my pbuilder skips this test so it wasn't caught: http://labs.seravo.fi/~otto/mariadb-repo/mariadb-10.0-sid-i386/mariadb-10.0_10.0.14-3_amd64.build-7b8f5e6-pbuilder.log plugins.unix_socket

Bug#769865: [debian-mysql] Bug#769865: mariadb-10.0: FTBFS on i386

The latest upload if mariadb-10.0 failed during the testsuite on i386: https://buildd.debian.org/status/package.php?p=mariadb-10.0 https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0arch=i386ver=10.0.14-3stamp=1416208329 A number of architectures are still building at this point, so

Bug#771213: [debian-mysql] Bug#771213: mariadb-server-10.0: file conflict with mysql-client-5.5

Thanks for reporting this! I mysql-5.5/5.6 the mysql_plugin is part of the client package: mysql-client-5.6.install:usr/bin/mysql_plugin mysql-client-5.6.manpages:debian/tmp/usr/share/man/man1/mysql_plugin.1 In MariaDB it is part of server package:

Bug#772964: [debian-mysql] Bug#772964: mariadb-10.0: FTBFS on mips, mipsel, powerpc

Hello! This is potentially fixed in http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=3b66ec189bdda12c2bf899fec87fcff7ee4f2bbf but I need to upload to experimental first to confirm it.. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of

Bug#773030: [debian-mysql] Bug#773030: mariadb-server-10.0: fails to install: rm: cannot remove '/var/lib/mysql/debian-*.flag': No such file or directory

Hello! 2014-12-13 14:35 GMT+02:00 Andreas Beckmann a...@debian.org: during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. Thanks for taking the time to review the piuparts

Bug#775882: [debian-mysql] Bug#775882: mariadb-10.0: affected by CVEs of the Oracle Patch Update for January 2015?

The page https://mariadb.com/kb/en/security/ has updated and includes info about these latest CVEs. It seems most issues were fixed in 5.5.41/10.0.16. One was for 5.5.39/10.0.13. 10.0.16 hasn't been yet released, but I'll expect it is released soon and I will try to be as fast as possible in

Bug#775882: [debian-mysql] Bug#775882: Bug#775882: mariadb-10.0: affected by CVEs of the Oracle Patch Update for January 2015?

Muchembled ] * Fix inclusion of Mroonga TokuDB plugins in mariadb-server-10.0 [ Otto Kekäläinen ] * Imported Upstream version 10.0.16. Inludes fixes for the following security vulnerabilities: - CVE-2015-0411 - CVE-2015-0382 - CVE-2015-0381 - CVE-2015-0432 - CVE-2014-6568

Bug#775882: [debian-mysql] Bug#775882: mariadb-10.0: affected by CVEs of the Oracle Patch Update for January 2015?

2015-01-27 8:09 GMT+02:00 Salvatore Bonaccorso car...@debian.org: Thanks for the update and checking with upstream regarding the two other CVEs. 10.0.16 seems now avaiable[1] (even though not yet announced on the webpage itself). [1]

Bug#775882: [debian-mysql] Bug#775882: mariadb-10.0: affected by CVEs of the Oracle Patch Update for January 2015?

Here is the reply from a MariaDB core developer: 2015-01-26 21:39 GMT+02:00 Sergei Golubchik s...@mariadb.org: Hi, Otto! On Jan 26, Otto Kekäläinen wrote: Hello Sergei! The page https://mariadb.com/kb/en/mariadb/security/ does not mention the ones Salvatore asks about below: 0385 and 0409

Bug#775882: [debian-mysql] Bug#775882: mariadb-10.0: affected by CVEs of the Oracle Patch Update for January 2015?

Status: The test suite failed. I found out that the cacert.pem that is part of the test suite expired today at 6 am UTC. I am working with devs to get this cert re-issued and test suite successful again. I did upload https://buildd.debian.org/status/package.php?p=mariadb-10.0suite=experimental

Bug#775882: [debian-mysql] Bug#775882: mariadb-10.0: affected by CVEs of the Oracle Patch Update for January 2015?

I started to search information about this 2 days ago, but so far I haven't found any indication that these would affect MariaDB, though I haven't got the definitive final reply from mariadb devs confirming so either. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a

Bug#779873: [debian-mysql] Bug#779873: mariadb-server-core-10.0: missing breaks+replaces mysql-client-5.[56] for /usr/bin/innochecksum takeover

Cool, I didn't know that piuparts also test mysql-mariadb migration scenarios. Issue fixed in git now. Thanks for reporting! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#782645: [debian-mysql] Bug#782645: and this broke my mariadb completely

Hello Josef! 2015-04-20 21:44 GMT+03:00 Josef Moosbauer jo...@mail.moosbauer.net: # But packages for MariaDB take priority Package: * Pin: Origin http://tweedo.com/ Pin-Priority: 1000 Looking at your sources listing I can see that you are mixing repositories for both wheezy and jessie, and

Bug#787533: [debian-mysql] Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

Hello! 2015-06-02 18:07 GMT+03:00 Andreas Beckmann a...@debian.org: .. during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files This my.cnf modification was introduced in

Bug#789323:

Please install the latest official Debian package of MariaDB and this issue will not exist. If you want to use .deb packages from other sources, please don't file bugs against Debian in those cases. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of

Bug#787533: [debian-mysql] Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

2015-06-11 21:56 GMT+03:00 Andreas Beckmann a...@debian.org: This my.cnf modification was introduced in commit https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=90b6bde63c8128eb7f54f16dfeec88081e4bdb0d That is, sorry, so utterly wrong ... Renaming the old my.cnf must be

Bug#787533: [debian-mysql] Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

Hello! mysql-5.6 is now in unstable, but it has many problems and does not seem to arrive in testing any soon..? https://tracker.debian.org/pkg/mysql-5.6 When mysql-5.6 is in testing it should be safe for me to remove the temporary mv line from mariadb-10.0 in favour of only using the

Bug#787533: [debian-mysql] Bug#787533: Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

2015-07-19 23:16 GMT+02:00 Otto Kekäläinen o...@seravo.fi: I cannot however upload it until a fixed version of mysql-5.6 is uploaded and has entered 'testing', as the dependency on mysql-common 5.6.25 would make all mariadb-10.0 installations in Debian testing to fail. For the record: mariadb

Bug#792780: [debian-mysql] Bug#792780: Bug#792780: Bug#792780: mariadb-10.0: FTBFS on powerpc but succeded previously

Now the build passed successfully: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.0arch=powerpcver=10.0.20-3stamp=1437946958 There was however one failing test: connect.json_udf Conclusions: - this error has certain randomness - build should not complete if there is even a single test

Bug#792780: [debian-mysql] Bug#792780: Bug#792780: mariadb-10.0: FTBFS on powerpc but succeded previously

This has now been fairly well debugged with gdb stack traces and all, and from now on is tracked in upstream bug report at https://mariadb.atlassian.net/browse/MDEV-8536 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

2015-07-22 20:34 GMT+03:00 Andreas Beckmann a...@debian.org: On 2015-07-22 19:18, Andreas Beckmann wrote: What's the meaning of exit status 141? This seems to happen on all jessie-sid upgrade paths involving mariadb-server-10.0 The packages were built from my branch, so don't include your

Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

2015-07-22 22:56 GMT+03:00 Andreas Beckmann a...@debian.org: That one was fixed already in December in https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=3afe791ed47b897de8fa9be998a4217fc2a36bad Robie added recently in 6bc2c1a5 in mysql-5.6 an explicit 'exit 0' at the end

Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

I gave up on fixing the powerpc build failure for new and will upload package with all current changes: https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/log Great to see that we have so many contributors in this round of packaging! :) -- To UNSUBSCRIBE, email to

Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink

2015-07-22 13:54 GMT+03:00 Robie Basak robie.ba...@ubuntu.com: Hi Andreas, As always, thank you for looking into this! On Wed, Jul 22, 2015 at 12:48:49PM +0200, Andreas Beckmann wrote: move innochecksum manpage to mysql-server-core-5.6, too Please note that these may need to be

Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

2015-07-22 13:53 GMT+03:00 Andreas Beckmann a...@debian.org: and has entered 'testing', as the dependency on mysql-common 5.6.25 would make all mariadb-10.0 installations in Debian testing to fail. That won't work, mysql-5.6 and mariadb-10.0 will have to enter testing together or

Bug#792780: [debian-mysql] Bug#792780: mariadb-10.0: FTBFS on powerpc but succeded previously

The log indicates that the build runs OK but when the test suite is supposed to run nothing happens, almost like the binary would plain crash. I got access today to partch.debian.org and ran the identical build + testsuite but was not able to reproduce this: the test suite started OK and the

Bug#792780: [debian-mysql] Bug#792780: mariadb-10.0: FTBFS on powerpc but succeded previously

I was now able to reproduce it with the jessie schroot and I've done a trace etc: http://labs.seravo.fi/~otto/mariadb-repo/logs/powerpc/ I am chatting with upstream devs to get their analysis what might have broke in 10.0.20. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org

Bug#787533: [debian-mysql] Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

2015-07-17 13:55 GMT+03:00 Andreas Beckmann a...@debian.org: git://git.debian.org/users/anbe/tmp/mariadb-10.0.git Andreas Beckmann (4): mariadb-common: make mysql-common dependency versioned mariadb-common.postinst: drop fallback my.cnf symlink management simplify

Bug#804336: [debian-mysql] Bug#804336: Galera-3: Embedded code copy used

Hello! I can see the failing builds at https://buildd.debian.org/status/package.php?p=galera-3 But where can I find the sources for the uploads about version 25.3.12-2+b1 and +b2 ? Or do these numbers simply stand for a rebuild of the same sources? How do I get the person who did these changes

Bug#805118: [debian-mysql] Bug#805118: galera-3: FTBFS on s390x

It seems the test suite on s390x failed, and at least this error is visible in the log: g++ -o .sconf_temp/conftest_7.o -c -Wno-long-long -Wno-deprecated -ansi -pipe -g -O3 -DNDEBUG -mzarch -march=z196 -mtune=zEC12 -Wall -Wextra -Wno-unused-parameter -D_FORTIFY_SOURCE=2 -pthread

Bug#802874: [debian-mysql] Bug#802874: mariadb-10.0: Various security fixes from 10.0.22 release

I have uploaded 10.0.22 to Sid today. For Jessie I have imported the new upstream release on the Jessie branch and done the related changes and light testing: http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/log/?h=jessie Github mirror for easy pull request submissions at

Bug#797238: [debian-mysql] Bug#797238: galera-3 ftbfs in unstable

This issue was already fixed in commit http://anonscm.debian.org/cgit/pkg-mysql/galera-3.git/commit/?id=3ccca8f62609bd310d670de0fc96065466eaa2e8 I see your patch also contains diagnostic lines. If you want those included in the package, please rebase your patch on the current git master at

Bug#787533: [debian-mysql] Bug#787533: Bug#787533: Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

2015-08-14 11:18 GMT+03:00 Otto Kekäläinen <o...@seravo.fi>: > For the record: mariadb-10.0 with these changes was uploaded to > unstable weeks ago, but it cannot enter testing, as it now has a > versioned dependency on mysql-5.6, which due to other problems in that > pack

Bug#787533: mariadb-common: modifies conffiles (policy 10.7.3): /etc/mysql/my.cnf

2015-09-08 12:26 GMT+03:00 Andreas Beckmann : >> Andreas: are you still into making mysql-common a separate source >> package as you suggested in the summer? I think it would be a good >> time now. > > Ack, I'm in :-) Great!

Bug#799150: [debian-mysql] Bug#799150: galera-3: FTBFS: undefined reference to `subunit_test_start'

Thanks for looking into Galera builds. I have reported this upstream at https://github.com/codership/galera/issues/346 I have also multiple other build failure bugs at upstream open that I don't know how to solve myself. One gcc-5 issue was solved in the upload today, but new ones apparently

Bug#797238: [debian-mysql] Bug#797238: Bug#797238: galera-3 ftbfs in unstable

Currenlty builds OK on all primary platforms: https://buildd.debian.org/status/package.php?p=galera-3

Bug#799150: galera-3: patch

Hello! Thanks for the patch. Upstream has also patches available, so I posted the info about your patch at https://github.com/codership/galera/issues/321 and we'll see which of the patches upstream recommends to applying.

Bug#805118: [debian-mysql] Bug#805118: galera-3: FTBFS on s390x

I just uploaded a new upstream version and it seems to also fix s390x builds.

Bug#804336: [debian-mysql] Bug#804336: fixed in galera-3 25.3.12-3

2015-11-13 23:26 GMT+02:00 Kurt Roeckx : > You actually build-depend on boost that provides that library. I > see no good excuse for not using the version provided by boost. Upstream devs say they don't see asio as real library, rather just as a header file. Switching to using

Bug#814944: [debian-mysql] Bug#814944: mariadb-connect-engine-10.0: ODBC support apparently not compiled in

Hello! Thanks for reporting you need this. The fix has not been backported to Jessie. We need a good motivation which the ftp masters accept before we can push a change to a stable release.

Bug#815746: Digikam should depend on virtual-mysql-server-core to support MariaDB

Package: digikam Severity: grave In http://anonscm.debian.org/viewvc/pkg-kde/kde-extras/digikam/trunk/debian/control?view=markup on line 22 Digikam defines as build dependency: mysql-server-core-5.5 | mysql-server-core This should be changed to: mysql-server-core-5.6 |

Bug#815567: Amarok should depend on virtual-mysql-server-core to support MariaDB

Package: amarok Severity: grave On line http://anonscm.debian.org/cgit/pkg-kde/kde-extras/amarok.git/tree/debian/control#n20 Amarok defines as build dependency: Build-Depends-Indep: mysql-server-core-5.6 | mysql-server-core This should be changed to: Build-Depends-Indep: mysql-server-core-5.6

Bug#812812: MySQL client library should ship a symbols file, or at least not have a Lintian override to hide the problem

Package: mysql-5.6 Version: 5.6.28-1 Severity: serious The mysql-5.5 source package produces the libmysqlclient18 shared library, main file being libmysqlclient.so.18. So does the mysql-5.6 package too (even using the same "18" version string oddly, are there no changes in the ABI?). It seems

Bug#815377: [debian-mysql] Bug#815377: mariadb-10.0: newly split out plugin packages need Breaks+Replaces: mariadb-server-10.0

Hello! Thanks for keeping an eye on Piuparts and spotting this. We had breaks+replaces only for old plugin packages and we completely overlooked the need for breaks+replaces for the server package. I have now fixed this in git and it will be included in next upload - soon.

Bug#814944: [debian-mysql] Bug#814944: mariadb-connect-engine-10.0: ODBC support apparently not compiled in

Tracked upstream as https://jira.mariadb.org/browse/MDEV-9684

Bug#816492: [debian-mysql] Bug#816492: galera-3: Galera fails to build with pbuilder for armhf (on amd64)

Severity: wishlist Please note that galera-3 in Debian is available only in unstable and testing at the moment: https://packages.debian.org/search?keywords=galera-3=names=all=all Filing a bug about Jessie is a whishlist type of an issue as galera-3 is not available on Jessie. Galera builds fine

Bug#815567: Amarok should depend on virtual-mysql-server-core to support MariaDB

2016-04-24 19:30 GMT+03:00 SamuelOPH : > I've got the impression that you mean asking for the mysql team to package > mysql-server-core and mariadb-server-core wouldn't be a solution, is that > right? If so, why? If Andreas recommends it, I can bake a mariadb-server-core

Bug#823325: mariadb-10.0: Various security fixes from 10.0.25 release

Acknowledged. I started working on the updates on Saturday but my build/test machine broke down and I haven't yet successfully rescued the btrfs file system on it. I intend to to the upgrades ASAP but right now I cannot promise a schedule, sorry.

Bug#832994: [debian-mysql] Bug#832994: libmariadbclient-dev-compat: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/libmysqlclient.so (from libmariadb-client-lgpl-dev-c

Thanks for spotting this. It should be fixed in https://anonscm.debian.org/gitweb/?p=pkg-mysql/mariadb-10.0.git;a=commitdiff;h=4c9104d2b40df4b8619b0a81cd346719d242a334

Bug#831229: [debian-mysql] Bug#831229: libmariadbclient-dev{, -compat}: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config, /usr/lib/*/libmysqlclient.so

Hello! This was fixed last week in http://anonscm.debian.org/cgit/pkg-mysql/mariadb-client-lgpl.git/commit/?id=c53120f7d4755291a0ec47a7c466e44794bcc3ad but not uploaded yet.

Bug#830707: [debian-mysql] Bug#830707: mariadb-connector-c: FTBFS on all architectures other than amd64 and i386

_ > pkg-mysql-maint mailing list > pkg-mysql-ma...@lists.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#832994: [debian-mysql] Bug#832994: libmariadbclient-dev-compat: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/libmysqlclient.so (from libmariadb-client-lgpl-dev-c

Correct link format: https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=4c9104d2b40df4b8619b0a81cd346719d242a334 Uploaded in 10.0.26-3. Closing issue.

Bug#832931: mariadb built successfully on powerpc

It seems this is still not fixed, so I filed it upstream: https://jira.mariadb.org/browse/MDEV-11877

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#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#852709:

See also discussion at https://github.com/ottok/mariadb-10.1/pull/8

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#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#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#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#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#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#855935: 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#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#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#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#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#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#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#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#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#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#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?).

Bug#857444: [debian-mysql] Bug#857444: Bug#857444: Bug#857444: mysql-server-5.5: upgrade from jessie to stretch leaves mysql server uninstalled

2017-03-15 10:14 GMT+02:00 Lars Tangvald : > When I did a quick test, I just replaced jessie with stretch in > /etc/apt/sources.list, ran apt-get update and apt-get dist-upgrade I've done this upgrade test many times over and it works well. We need more details about

Bug#857444: [debian-mysql] Bug#857444: Bug#857444: mysql-server-5.5: upgrade from jessie to stretch leaves mysql server uninstalled

Hello! >> One way to make this an easier transition would be to have a >> mysql-server package in stretch that's a dummy package that depends >> on >> default-mysql-server, and that has an upgrade notice about the >> transition to mariadb that is happening. The transition is supposed to be

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

For the record: 2017-01-05 8:07 GMT+02:00 Salvatore Bonaccorso : > Hi > > When installing myssql-server-5.6 in stretch and sid, then mysqld is > started and listend not binding on localhost only, but listen on *. > > tcpLISTEN 0 80 :::mysql:::*

Bug#855244: [debian-mysql] Bug#855244: libmariadbclient-dev: hardcoded -lmysqlclient, package not providing it though

Hello Michael! I am not sure what the actual problem here is. What are you trying to achieve which does not work? What is the name of the software that fails to compile with MariaDB, either using libmariadbclient-dev, libmariadbclient-dev-compat, libmariadb-dev or libmariadb-dev-compat? To my

  1   2   3   4   >