Bug#830572: Support x.y.z-2 UNRELEASED type of changelog opening commits

Package: git-buildpackage Severity: wishlist Current snapshot number style workflow supported by git-buildpackage does not fit my workflow. I'd wish there was a option like 'git-dch --unreleased' which simply added to the changelog an empty entry with the Debian revision incremented by one and

Bug#804992: [debian-mysql] Bug#804992: Bug#804992: mysql-server-5.6: Please drop dependency on initscripts package

Hello! 2016-07-09 11:08 GMT+03:00 Michael Biebl : >> We're expecting to upload 5.7 to experimental very soon now. If somebody >> wants to cherry-pick this to 5.6 and upload, I have no particular >> objection (though please push to VCS too; we haven't moved 5.6 into the >>

Bug#829491: mariadb-server-10.0: Removes lost+found directory if purged, /var/lib/mysql is a mountpoint with an ext4 filesystem, and user requests to remove all databases

Hello Axel! I committed your patch in https://github.com/ottok/mariadb-10.0/commit/fddb4c3d2a74d25c5aef057674d561fbc874d14c on my own development branch. Packages built from that commit are now available at # Debian unstable deb http://labs.seravo.fi/~otto/mariadb-repo/

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

2016-07-03 23:07 GMT+03:00 Axel Beckert : > My only ideas so far: > > * Maybe a longer timeout to wait for the shutdown could help? (If > there's some kind of timeout at all.) > * Maybe trying to stop it a second time after some short "sleep"? Stopping is done by invoking the

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

Thanks for looking into MariaDB. 2016-07-03 21:42 GMT+03:00 Axel Beckert : > Removing mariadb-server-10.0 (10.0.26-1) ... > [FAIL] Stopping MariaDB database server: mysqld failed! > invoke-rc.d: initscript mysql, action "stop" failed. > dpkg: error processing package

Bug#829491: mariadb-server-10.0: Removes lost+found directory if purged, /var/lib/mysql is a mountpoint with an ext4 filesystem, and user requests to remove all databases

Hello! Thanks for your report. The problem is that the purge section in the postrm script does a simple rm, which works OK if the directory is a normal directory, but not if it is a mountpoint. The postrm script does not have any kind of mountpoint detection or conditional handling for that

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

I have forwarded this upstream at https://github.com/codership/galera/issues/407 Upstream thinks this is a generic libasio-dev / openssl issue, in which case you'll have a lot of software breaking.

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#815599: [debian-mysql] Bug#815599: mariadb-server-10.0: Postinstall script does not clear the mysql-server/root_password_again field

Owen, Would you like to cook up at patch for this?

Bug#826879: mariadb-10.0: French debconf templates translation

Merci! French translation updated in commit http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=908656d3918836f0bcb18ca3d8140be997d2d9b1

Bug#824487: mariadb-10.0: [INTL:de]

2016-05-23 15:56 GMT+03:00 Chris Leick : > # FIXME s/indicated/indicates/ Fixed in commit: https://github.com/ottok/mariadb-10.0/commit/340f6350e3372646962df394a0931ddc75dc8e3e

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#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#817263: [debian-mysql] Bug#817263: Removed package(s) from unstable

Hello! 2016-03-10 10:22 GMT+02:00 Adam D. Barratt : >> Oh crap. Now all of our build logs (very important to debug various >> build/testsuite failures and their occurences on different platforms) >> have been lost, > > >

Bug#817263: About ftp-master processes and #817263: mariadb-10.0 removed from unstable

Hello Andreas and ftp-masters! First, thanks to Andreas for looking after the mariadb-10.0 package and helping with it. However, please note that your bug report #817263 did not reach the maintainers/uploaders of the mariadb-10.0 package and we had no idea that you where requesting cruft removal

Bug#817263: [debian-mysql] Bug#817263: Removed package(s) from unstable

2016-03-10 0:13 GMT+02:00 Debian FTP Masters : > We believe that the bug you reported is now fixed; the following > package(s) have been removed from unstable: mariadb-10.0 Oh crap. Now all of our build logs (very important to debug various build/testsuite

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#810968: [debian-mysql] Bug#810968: Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

Hello Lennart! I asked core developers to review this and got this reply: It's probably alright for 10.0. But it's not completely suitable for 10.1. As contributor mentioned himself that there's a problem with this patch: "When mysqld is called without mysqld_safe". I'd rather simplify

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#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#810968: [debian-mysql] Bug#810968: Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

Hello Lennart! Do you intend to make one more version of the patch so that it is perfect and it is safe for me to include it in the next upload? Thanks for your help! 2016-01-26 11:13 GMT+02:00 Otto Kekäläinen <o...@seravo.fi>: >> 2) Check the parent process id being 1 >>I

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#812052: [debian-mysql] Bug#812052: Bug#812052: galera-3: FTBFS with GCC 6: C++11 requires a space between..

Upstream issue entry: https://github.com/codership/galera/issues/384

Bug#810968: [debian-mysql] Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

> 2) Check the parent process id being 1 >In this case parent of the parent because of mysqld_safe ># test $(ps -o ppid= -p $(ps -o ppid= -p $PID)) -eq 1 >This would work in most cases I can think of. mysqld run by a user >or a container would not be started by the init. But seems

Bug#797210: [debian-mysql] mariadb-10.0: mariadb-server does not ship a debconf set for creating a adminitrative user (like mysql-server do)

2016-01-26 12:38 GMT+02:00 Carsten Schoenert : >> I skimmed through >> https://people.debian.org/~seanius/policy/dbconfig-common.html/ but >> didn't really get the hang of it. The docs are written for "consumers" >> and not "providers" like the mariadb-10.0 package

Bug#797210: [debian-mysql] mariadb-10.0: mariadb-server does not ship a debconf set for creating a adminitrative user (like mysql-server do)

2016-01-26 13:53 GMT+02:00 Carsten Schoenert : > Don't care about packages that need to set up databases, just provide > with mariadb-server all possible authentication methods and guide the > user while installing your package. > And maybe provide a dbconfig way to add

Bug#810968: [debian-mysql] Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

Thanks Lennart, the patch is much nicer to read now. It seems to rely on the fact that it should find the line 'pid-file = /var/run/mysqld/mysqld.pid' in the file /etc/mysql/my.cnf However, since the new mysql/mariadb config decoupling effort (driven by Ubuntu developers) the file

Bug#797210: [debian-mysql] Bug#797210: mariadb-10.0: mariadb-server does not ship a debconf set for creating a adminitrative user (like mysql-server do)

Carsten, You reported this with severity important: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797210 Please provide more information as requested in my last comment. I don't know what to do about this or what the concrete problem/failure is. Please advice.

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#812052: [debian-mysql] Bug#812052: galera-3: FTBFS with GCC 6: C++11 requires a space between..

Thanks for reporting, I have forwarded this to upstream developers.

Bug#810968: [debian-mysql] Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

Thanks for reporting this and supplying a patch! Can you please make a new version where the scipt block has some comments? There is rather complex stuff going on and somebody reviewing it would have an easier time if they can from the comments see what the code is supposed to do, and then read

Bug#793977: [debian-mysql] Bug#793977: mariadb-server-core-10.0: please include mysql_upgrade for application started mariadb server

Hello! I now did this change: http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=3ff0aa39825e3f9d0f7232f5bb5ba063f5473edf The my-default.cnf referred here https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1422391 does not seem to exist in MariaDB, so I am not adding it

Bug#773727: [debian-mysql] Bug#773727: Bug#773727: mariadb-server-10.0: Mroonga & TokuDB plugins missing

Hello! I have now implemented this. Please review latest git commits (http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git), in particular: http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=7a3739d903e2e2584660544c5ab2545f7f9d4447

Bug#793977: [debian-mysql] Bug#793977: mariadb-server-core-10.0: please include mysql_upgrade for application started mariadb server

Hello! 2016-01-08 4:25 GMT+02:00 Robie Basak : > So I don't know what you mean by "double entries in install file" (I > haven't looked), but the rest of what you describe is I believe > intentional and correct. Well, if you looked it would be obvious:

Bug#773727: [debian-mysql] Bug#773727: Bug#773727: Bug#773727: mariadb-server-10.0: Mroonga & TokuDB plugins missing

I experimented a bit in this direction with http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=97b3c442f51e51abfb2fe053f5463d632e5b34b0 Comments?

Bug#800009: [debian-mysql] Bug#800009: Bug#800009: Workaround found

This issue is now fixed in 10.0.23-1 as the passwordless root account authenticated via unix socket is only used on fresh installs. Old installs will continue to use any root password previously set.

Bug#797210: [debian-mysql] Bug#797210: mariadb-10.0: mariadb-server does not ship a debconf set for creating a adminitrative user (like mysql-server do)

Hello! 2015-08-28 21:51 GMT+03:00 Carsten Schoenert <c.schoen...@t-online.de>: > Hello, > > On Fri, Aug 28, 2015 at 08:58:46PM +0300, Otto Kekäläinen wrote: >> MariaDB uses socket authentication in Debian unstable. That is an >> important feature that increases securi

Bug#773727: [debian-mysql] Bug#773727: Bug#773727: mariadb-server-10.0: Mroonga & TokuDB plugins missing

Arnaud: any chance of progress for this one?

Bug#809022: [debian-mysql] Bug#809022: TODO: Add autopkg tests to detect changes introduced by other uploaded packages

Hello! 2015-12-26 14:55 GMT+02:00 Jonathan Aquilina : > Good Afternoon Otto, > > Are you on IRC at all? My nick is otto at the moment on OFTC. Please ping me there or send email.

Bug#809022: [debian-mysql] Bug#809022: TODO: Add autopkg tests to detect changes introduced by other uploaded packages

Hello! 2015-12-26 14:55 GMT+02:00 Jonathan Aquilina : > Good Afternoon Otto, > > Are you on IRC at all? > > Jonathan Aquilina Yes, I am idling on irc an check my awaylog maybe once a week. Normally you'll reach me faster by e-mail, as I check my email maybe 100 times a

Bug#809022: TODO: Add autopkg tests to detect changes introduced by other uploaded packages

Package: mariadb-10.0 Severity: wishlist This is a TODO item for MariaDB packaging. Feel free to start working on it if you want to contrbute to Debian and MariaDB. Task: Add autopkg tests to detect changes introduced by other uploaded packages 1. Read up on http://ci.debian.net/doc/ 2. Fork

Bug#808419: TODO: Add debconf question to make feedback plugin opt-in very easy

Package: mariadb-10.0 Severity: wishlist This is a TODO item for MariaDB packaging. Feel free to start working on it if you want to contrbute to Debian and MariaDB. Task: Add debconf question to make feedback plugin opt-in very easy while running 'apt-get install mariadb-server' The code would

Bug#808420: TODO: Implement systemd scripts

Package: mariadb-10.0 Severity: wishlist This is a TODO item for MariaDB packaging. Feel free to start working on it if you want to contrbute to Debian and MariaDB. Task: Implement systemd scripts for MariaDB Currently the package ships only with traditional init/upstart scripts. We should

Bug#808421: TODO: Implement metadata.yml (DEP12)

Package: mariadb-10.0 Severity: wishlist This is a TODO item for MariaDB packaging. Feel free to start working on it if you want to contrbute to Debian and MariaDB. Task: Implement metadata.yml DEP12. Confirm with Duck that all URLs are functional. Read more at:

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#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#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#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#801959: Tag mariadb packages with debtags

Package: mariadb-10.0 Severity: whishlist This is a TODO item for myself or anybody who wishes to help out with mariadb packaging. Currently all mariadb-packages are missing debtags: http://debtags.debian.net/reports/maint/pkg-mysql-ma...@lists.alioth.debian.org At least basic debtags should be

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#800009: [debian-mysql] Bug#800009: mariadb-server-10.0: Assumes root has no password without ensuring this is true

Hello! 2015-09-25 11:56 GMT+03:00 Matijs van Zuijlen : > Package: mariadb-server-10.0 > Version: 10.0.21-3 > Severity: normal > > I upgraded to mariadb from mysql. My mysql root user had a password, but > mariadb assumes it does not and now I get errors in my log like so, : > >

Bug#800009: [debian-mysql] Bug#800009: Workaround found

2015-09-25 12:51 GMT+03:00 Matijs van Zuijlen : > Given that mariadb ships with a tool that sets a password on the root user, > this > situation is suboptimal. > > The MariaDB startup scripts should allow root to be identified either way, and > allow the system administrator to

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#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#793316: [debian-mysql] Bug#793316: transition: mysql-5.6

2015-09-14 13:11 GMT+03:00 Robie Basak : > The Debian MySQL Maintainers team is prepared to do option 1, but it > seems you are not. I do not consider any of the other options to be > acceptable. For the record, I support Robie on this. The packages mysql and mariadb have

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#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#798048: [debian-mysql] Bug#798048: mariadb-10.0: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

2015-09-04 22:54 GMT+03:00 Adriano Rafael Gomes : > Please, Could you update the Brazilian Portuguese Translation? > > Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is > tested with msgfmt and podebconf-display-po. I kept on old translator in the

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#773727: [debian-mysql] Bug#773727: Bug#773727: mariadb-server-10.0: Mroonga TokuDB plugins missing

Hello! 2015-02-27 8:31 GMT+02:00 Arnaud Fontaine ar...@debian.org: Great. I don't think it's an urgent task but I will start splitting up the package when I have some time if that's ok with you? Do you think you might have some time now..? :)

Bug#797210: [debian-mysql] Bug#797210: mariadb-10.0: mariadb-server does not ship a debconf set for creating a adminitrative user (like mysql-server do)

MariaDB uses socket authentication in Debian unstable. That is an important feature that increases security and makes administration easier. In the majority of cases you don't need or want to make a root user, only user accounts that have limited and intended access to the database. I don't know

Bug#797004: [debian-mysql] Bug#797004: mysql-server 5.5.44-0+deb8u1 not installable on fresh install of Stretch

Downgrading from MariaDB 10.0 or MySQL 5.6 back to old MySQL 5.5 isn't supported and in many cases impossible. If you want to do that, then purge the old installation so that there are no configs or databases of the new format left behind, and then install MySQL 5.5. from scratch.

Bug#797004: [debian-mysql] Bug#797004: mysql-server 5.5.44-0+deb8u1 not installable on fresh install of Stretch

2015-08-26 22:40 GMT+03:00 Randy thejun...@gmail.com: Trying to setup MythTV which requires mysql-server. Tried to install and it I don't see that there even is any package mythtv in Debian. https://packages.debian.org/search?keywords=mythtvsearchon=namessuite=allsection=all Are you using some

Bug#797004: [debian-mysql] Bug#797004: mysql-server 5.5.44-0+deb8u1 not installable on fresh install of Stretch

2015-08-26 23:25 GMT+03:00 Randy thejun...@gmail.com: On Wednesday, August 26, 2015 11:10:24 PM you wrote: 2015-08-26 22:40 GMT+03:00 Randy thejun...@gmail.com: Trying to setup MythTV which requires mysql-server. Tried to install and it I don't see that there even is any package mythtv in

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#793977: [debian-mysql] Bug#793977: mariadb-server-core-10.0: please include mysql_upgrade for application started mariadb server

Hello! Thanks for taking the time to write a good bug report and investigate the situation. Indeed, mysql_upgrade is at the moment shipped in the mariadb-server-10.0 package and triggered from its postinstall scripts and in certain situations from the init script (the debian-start is called from

Bug#788530: Entr in Debian

Hello! I'm a contributor to Entr RPM packaging and I can help with maintenance in Debian too if you want, but I am only a Debian Maintainer, not DD. Do you have a git repo where we can collaborate? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

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#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#793316: [debian-mysql] Bug#793316: transition: mysql-5.6

2015-07-23 13:15 GMT+03:00 Robie Basak robie.ba...@ubuntu.com: On Thu, Jul 23, 2015 at 10:59:15AM +0200, Emilio Pozuelo Monfort wrote: Didn't we agree that we would release Stretch with only mariadb? When do you plan to start working on that so we can drop mysql-* from testing? No, that was

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-dist-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 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

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#790249: [debian-mysql] Bug#790249: mysql-server: Upgrade 5.5 to 5.6 fails

As mariadb-10.0 packaging is based on mysql-5.6 packaging (since about 2 years ago when Nicolas Bamber et al had put a lot of effort in making it much better than the mysql-5.5 packaging), all packaging bugs that have been fixed in mariadb-10.0 should be reviewed and ported over to mysql-5.6. For

Bug#792918: [debian-mysql] Bug#792918: mariadb-10.0: upgrade fails when /var/lib/mysql is a soft link

2015-07-21 9:03 GMT+03:00 Israel Tsadok itsa...@gmail.com: Looks like you were the one who removed it: https://github.com/ottok/mariadb-10.0/commit/f7caa041db74f3db703d9342ddae5e8c584d87b4 I guess you either clean up too much, or not enough... Thanks a lot for spotting this! I now recovered

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#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#787118: [debian-mysql] Bug#787118: mariadb-server-10.0: Compile with OpenSSL (instead of YaSSL)

See also https://mariadb.atlassian.net/browse/MDEV-6823 CYaSSL cannot be used until MariaDB core developers confirm that it is feature complete enough to work with MariaDB (and vice versa MariaDB is compatible with the CYaSSL API). OpenSSL cannot be used unless OpenSSL users give an explicit

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

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#792123: [debian-mysql] Bug#792123: mariadb-common: utf8 4-bit character set

2015-07-20 23:07 GMT+03:00 Olaf van der Spek olafvds...@gmail.com: Feel free to open a pull request on Github (against https://github.com/ottok/mariadb-10.0) for this or any other spell checking and you will get the git log credits for your contribution. I can also easily run 'git pull

Bug#792918: [debian-mysql] Bug#792918: mariadb-10.0: upgrade fails when /var/lib/mysql is a soft link

Hello! Thank you for filing this excellent report. Since you seem to know how to solve it, would you like to open a pull request at github and have your contribution logged in git history? The Debian packaging repo http://git.debian.org/?p=pkg-mysql/mariadb-10.0.git is mirrored at t

Bug#792918: [debian-mysql] Bug#792918: mariadb-10.0: upgrade fails when /var/lib/mysql is a soft link

Thank you for your PR at https://github.com/ottok/mariadb-10.0/pull/25 I will merge it and after that it will automatically be available in Debian unstable and eventually in new releases of Debian and Ubuntu. Due to Debian and Ubuntu policies it is difficult to backport these kind of changes and

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#792123: [debian-mysql] Bug#792123: mariadb-common: utf8 4-bit character set

2015-07-11 20:03 GMT+03:00 Olaf van der Spek olafvds...@gmail.com: +# MySQL/MariaDB default is Latin1, but in Debian we rather default to the full +# utf8 4-bit character set. See also client.cnf 4 bits isn't much, did you mean 4 bytes? Thank you for spotting the typo. Feel free to open a

Bug#789589: [debian-mysql] Bug#789589: +1

2015-07-06 19:14 GMT+03:00 Olaf van der Spek o...@xwis.net: I don't see it being stopped: That is probably because you are running dpkg to configure two not fully configured packages, thus dpkg does do the full restart cycle of the service. I just tested, here is how it looks in a normal

Bug#789589: [debian-mysql] Bug#789589: +1

2015-07-06 17:33 GMT+03:00 Olaf van der Spek o...@xwis.net: On 3-7-2015 16:13, Otto Kekäläinen wrote: This should now be fixed in commit https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/debian/mariadb-server-10.0.postinst Oops, here is the full link https

Bug#739846: [debian-mysql] Bug#739846: Bug#739846: invoke-rc.d: initscript mysql, action start failed.

Hello! 2015-06-30 11:35 GMT+03:00 Bob Proulx b...@proulx.com: I had also modified /etc/mysql/debian-start (hey it is a conffile after all) to avoid printing this message: echo Checking for tables which need an upgrade, are corrupt or were echo not closed cleanly. This and many similar

Bug#789589: [debian-mysql] Bug#789589: +1

2015-06-27 1:35 GMT+03:00 Olaf van der Spek o...@xwis.net: Hi, I might've hit the same issue: It is probably not the same issue, but the symptoms look similar. Setting up mariadb-server-10.0 (10.0.20-1) ... 150627 0:30:08 [Note] /usr/sbin/mysqld (mysqld 10.0.20-MariaDB-1) starting as

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#789589: [debian-mysql] Bug#789589: Bug#789589: mariadb-server-10.0: Infinite upgrade

2015-07-03 1:14 GMT+03:00 Otto Kekäläinen o...@seravo.fi: Basically what you Yuril did was removed all configuration and data files, and then installed. For some reason the mysqld daemon did not start on your system, and the failure became visible during an upgrade where the system restarts

Bug#789589: [debian-mysql] Bug#789589: Bug#789589: mariadb-server-10.0: Infinite upgrade

Hello! 2015-07-03 16:52 GMT+03:00 Yurii Kolesnykov yuriko...@gmail.com: I think I know the reason and a way to reproduce this. I still don't know how to reproduce the issue. You should put a copy-paste of your experience here. I have ran into same issue today when I have installed mariadb on

Bug#789589: [debian-mysql] Bug#789589: mariadb-server-10.0: Infinite upgrade

Basically what you Yuril did was removed all configuration and data files, and then installed. For some reason the mysqld daemon did not start on your system, and the failure became visible during an upgrade where the system restarts the service. I broke one installation on purpose, and this is

Bug#789589: [debian-mysql] Bug#789589: mariadb-server-10.0: Infinite upgrade

2015-06-22 14:52 GMT+03:00 Yurii Kolesnykov yuriko...@gmail.com: * What was the outcome of this action? Stuck at Configuring mariadb-server-10.0 Thanks for reporting this! Do you have any additional information what dpkg is stuck at? What version of MariaDB did you have previously? I can

Bug#789589: [debian-mysql] Bug#789589: Bug#789589: mariadb-server-10.0: Infinite upgrade

I've tracked this change to this commit: Author: Otto Kekäläinen o...@seravo.fi 2015-02-03 22:47:54 Committer: Otto Kekäläinen o...@seravo.fi 2015-02-04 00:03:55 Parent: 8c267579283fcbcfa307ef7aa062c222e9832140 (Update debconf translations to match new passwordless scheme) Child

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-dist-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! 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

<    8   9   10   11   12   13   14   15   >