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

Hi Andreas, Some quick answers (without looking at detail): On Fri, Jul 17, 2015 at 01:10:35PM +0200, Andreas Beckmann wrote: I pushed another one to deregister the my.cnf.fallback alternative on removal, otherwise purge gets noisy about the dangling link. Having looked at your previous

Bug#609537: /etc/init.d/mysql stop leaves a process but exits with 0 status

reassign 609537 mysql-server-5.5 thanks As far as I can tell this bug doesn't exist in the init.d script shipped with mysql-server-5.6 - I can see waiting code there similar to the code proposed in the patches in this bug. So presumably this should be tracked just in mysql-server-5.5 (which will

Bug#793358: mysql-5.6: FTBFS on HURD: error: 'RTLD_DEFAULT' undeclared

Hi, I've not included this in my upload today as I want to get it forwarded upstream. I'm speaking to upstream on Friday and I'd like to go through all the oustanding bugs that are relevant to upstream with them then. But if we don't get it resolved upstream soon we can carry the patch anyway I

Bug#804239: marked as pending

Hi Osamu, Thank you for the quick update. Did you intend to commit this to the "multitar" branch? I have managed to get uscan to work with your recent commits. Thank you! For the record, this is what works for me: version=3 opts=\

Bug#803922: No support for tipc

Package: iproute2 Version: 4.1.1-1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu xenial A new tool "tipc" was added to iproute2 v 4.1.1, needed for managing the TIPC kernel module, but this is not currently built. A downstream report says that this is because libmnl-dev is not a

Bug#691412: patch for the ntpd bug 2174

On Mon, Feb 23, 2015 at 05:03:16PM +0100, Roland Lammel wrote: > This patch is already included upstream in 4.2.8p1 (actually 4.2.7). stretch is on 1:4.2.8p4+dfsg-3 now so does that mean this is fixed? signature.asc Description: Digital signature

Bug#804239: [uscan] Failure when basename is in query string

Package: devscripts Version: 2.15.8 If the download URL is a query string, such as http://www.example.com/download?file=package-version.tar.gz, then uscan ends up downloading the file as package-version.download which subsequently causes mk-origtargz to fail with something like: Parameter

Bug#801746: mysql-server-5.6: Please run restorecon on directories you create (at boot and postinst) so it works with SE Linux

Hi Russell, Thank you for explaining this to me. On Thu, Oct 15, 2015 at 01:19:23PM +1100, Russell Coker wrote: > Every directory that is in a Debian package has it's context set by dpkg. So > if you were to add /var/lib/mysql/mysql and /var/log/mysql to the package > then > they would have

Bug#781257: snmp: preinst kills all processes of user snmp

On Thu, Mar 26, 2015 at 03:39:52PM +0100, Christian Seiler wrote: > 5. And finally: why is this even done? I simply don't see the point of > doing this... The commit message in git doesn't describe the need for > this change, and I can't imagine any scenario for this: snmp contains a > bunch of

Bug#801962: Invalid input fails to result in error return

Package: php5-json Version: 1.3.7-1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu wily Hi, As described by Ice downstream: "On a fundamental level, the provided replacement doesn’t match PHP Documentation about behaviour. Json_decode() is described to return NULL on invalid UTF-8

Bug#801746: mysql-server-5.6: Please run restorecon on directories you create (at boot and postinst) so it works with SE Linux

Hi Russell, Thank you for the patch. These sounds like quite a maintenance burden to me. It seems almost certain to me that this will regress if packaging changes, as it's unlikely that maintainers will remember to keep all the restorecon calls up to date. Please note that I am not familiar

Bug#793316: [debian-mysql] Bug#793316: transition: mysql-5.6

On Tue, Sep 08, 2015 at 11:03:28PM +0100, Jonathan Wiltshire wrote: > > The wish of the release team and security team has been to keep just > > one MySQL variant. If such a decision is made, it must be made above > > the pkg-mysql-maint team as the team will never be able to agree which > >

Bug#798126: mysql-5.6 FTBFS on mips64el

tags 798126 + pending thanks On Mon, Sep 21, 2015 at 01:04:26PM +0200, Aurelien Jarno wrote: > Ok, I understand. The patch has been lost somewhere in the mysql-5.5 to > mysql-5.6 transition, and the one in the 5.5 version actually has a > DEP3 headers. I just removed it by accident when

Bug#793316: [debian-mysql] Bug#793316: transition: mysql-5.6

On Wed, Sep 16, 2015 at 10:09:38PM +0100, Jonathan Wiltshire wrote: > Without wanting to point fingers, a significant source of opposition to > shipping more than one variant is the security team (with, IMO, fairly good > reasoning). In general the release team respects the wishes of the security

Bug#798126: mysql-5.6 FTBFS on mips64el

Hi Aurelien, On Sat, Sep 19, 2015 at 01:44:38AM +0200, Aurelien Jarno wrote: > I have seen that the patch hasn't been included in the latest upload. I > believe it was not clear enough which patch should be applied. Therefore > please find attached a patch which applies directly to the version in

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

On Thu, Jul 30, 2015 at 09:34:16AM +0300, Otto Kekäläinen wrote: > Solving this is _not_ straightforward (for me) because of two reasons: > 1) I personally never used just the core package and I don't fully > understand the motivation why it even exists. Is Akonadi the only use > case? > 2) The

Bug#793358: mysql-5.6: FTBFS on HURD: error: 'RTLD_DEFAULT' undeclared

Hi, On Sun, Dec 20, 2015 at 11:17:03AM +0100, Samuel Thibault wrote: > Samuel Thibault, on Fri 18 Sep 2015 09:20:39 +0200, wrote: > > merely putting the definition of _GNU_SOURCE before #includes (as it > > should always be) fixes the build, here is a tested patch. > > Ping? Thank you for the

Bug#793358: mysql-5.6: FTBFS on HURD: error: 'RTLD_DEFAULT' undeclared

tags 793358 pending thanks On Sun, Dec 20, 2015 at 01:42:37PM +0100, Samuel Thibault wrote: > > Upstream don't want to carry the patch as they can't test it, > > Well, the thing is: it does not even make *sense* to define _GNU_SOURCE > after having included headers!... To be fair to them, I

Bug#793358: mysql-5.6: FTBFS on HURD: error: 'RTLD_DEFAULT' undeclared

On Sun, Dec 20, 2015 at 02:39:13PM +, Robie Basak wrote: > tags 793358 pending > thanks My build machine appears broken right now. I was hoping to update to 5.6.28 at the same time, too. I may not get to it for a while as I'm on vacation, so in the meantime if someone else wants to

Bug#805828: mysql-server-5.6: upgrade didn't work, package unusable, mysql does not start

Hi, Do you have steps to reproduce this please? What makes you think it is a bug in the packaging as opposed to a configuration problem on your system? On Sun, Nov 22, 2015 at 10:02:05PM +0100, jpp wrote: > The /var/lib/mysql is a symlinj to another location on another disk. I'm not aware of

Bug#810796: HTTP pipelining is broken and causes download failures

Package: apt Version: 1.10 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu xenial apt enables pipelining by default. But it does not check to see if the server supports HTTP/1.1, so where the server doesn't apt is breaking the HTTP protocol by attempting to use pipelining. This causes

Bug#810796: HTTP pipelining is broken and causes download failures

Sorry, I failed to Cc: the bug. Done now, and bounced my original message to it also for the archive. signature.asc Description: Digital signature

Bug#810796: HTTP pipelining is broken and causes download failures

On Tue, Jan 12, 2016 at 02:36:28PM +0100, Julian Andres Klode wrote: > Well, yes, nobody really uses HTTP/1.0 servers, so it's not really tested > much. I just checked and a newer squid (3.1.19) that I have handy also responds with HTTP/1.0. I don't have a squid 3.4 deployment to check, but 3.1

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

On Sun, Jan 10, 2016 at 04:49:47PM +0200, Otto Kekäläinen wrote: > My point here was that I cannot simply copy what it looks like in > mysql-5.6 packaging, because it does not seem like a trustworthy model > in this case, so I wonder if something else in addition should be > moved to -core too?

Bug#811222: FTBFS: Can't use 'defined(@array)'

tags 811222 + wontfix thanks Hi Martin, On Sat, Jan 16, 2016 at 04:05:15PM -0800, Martin Michlmayr wrote: > Package: mysql-5.5 > Version: 5.5.44-0+deb8u1 > Severity: serious 5.5.44-0+deb8u1 will be removed from unstable shortly. It is not in testing. See bug #811158. It is superseded by

Bug#811443: mysql-5.6: Multiple security fixes from the January 2016 CPU

Question for the security team. On Mon, Jan 18, 2016 at 09:16:06PM +0100, Norvald H. Ryeng wrote: > Source: mysql-5.6 > Version: 5.6.27-2 > Severity: grave > Tags: security upstream fixed-upstream 5.6.27-2 only exists in testing, and I uploaded 5.6.28-1 to unstable recently. It hasn't landed in

Bug#811428: [debian-mysql] Bug#811428: Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

Hi Salvatore, On Tue, Jan 26, 2016 at 08:17:30PM +0100, Salvatore Bonaccorso wrote: > On Tue, Jan 26, 2016 at 06:36:06PM +0000, Robie Basak wrote: > > Hi Salvatore, > > > > On Tue, Jan 26, 2016 at 01:19:26PM +0100, Salvatore Bonaccorso wrote: > > > Thank you lo

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

Hi Otto, On Tue, Jan 26, 2016 at 10:03:37PM +0200, Otto Kekäläinen wrote: > 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

Bug#811428: [debian-mysql] Bug#811428: Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

On Wed, Jan 27, 2016 at 07:15:24PM +0100, Salvatore Bonaccorso wrote: > Yes the dak mails for security-master are only sent to the security > team. I can confirm that > > mysql-5.5_5.5.47-0+deb8u1_amd64.changes ACCEPTED into stable->embargoed > > and > > mysql-5.5_5.5.47-0+deb7u1_amd64.changes

Bug#813413: Upgrade from mysql-server-5.5 can break configurations that use the conf.d directory

reassign 813413 mysql-common tags 813413 + moreinfo thanks Hi Justin, On Mon, Feb 01, 2016 at 11:45:46AM -0600, Justin Pasher wrote: > In my opinion, the directories should be reversed so that the conf.d/ > directory is included last so it will properly override the defaults like > before.

Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

Dear Security Team, You have asked us to be prompt with helping to prepare security updates for you, and we have done so. We have kept the bug updated like you asked us last time. The sources are tested and ready. We notified the bug as requested, but haven't heard from you. Please let us know

Bug#811428: [debian-mysql] Bug#811428: Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

Hi Salvatore, On Tue, Jan 26, 2016 at 01:19:26PM +0100, Salvatore Bonaccorso wrote: > Thank you looks good to me. > > I haven't seen the same for jessie, but assuming it is basically the > same and matching what you showed me initially from git, let's go > ahead with an upload. FYI, we're still

Bug#812811: Incorrect permissions on device nodes

Package: debootstrap Version: 1.0.76 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu xenial Hi, mk-sbuild (from ubuntu-dev-tools) is creating chroots with a broken /dev/null (it is 644). This breaks sbuild for me. I believe this is due to a regression in debootstrap caused by your

Bug#811068: FTBFS: FAIL: check_vcnc: ../../test-driver: line 107: 77018 Aborted

tags 811068 + patch user ubuntu-de...@lists.ubuntu.com usertag 811068 + xenial ubuntu-patch thanks Quilt patch attached. Robie From: Robie Basak <robie.ba...@canonical.com> Date: Sun, 10 Apr 2016 19:03:00 + Subject: [PATCH 1/1] Accept SQLITE_INDEX_CONSTRAINT_LIKE from sqlite sqlite

Bug#811068: FTBFS: FAIL: check_vcnc: ../../test-driver: line 107: 77018 Aborted

forwarded 811068 https://bugzilla.gnome.org/show_bug.cgi?id=764860 thanks On Fri, Jan 15, 2016 at 03:31:24AM -0800, Martin Michlmayr wrote: > Package: libgda5 > Version: 5.2.4-1 > > libgda5 fails to build for me in unstable. Do you see this, too? We see this in Ubuntu. I've done some

Bug#819019: fake-hwclock: allow the saved time to go backwards under normal use

On Fri, Apr 08, 2016 at 06:49:35PM +0100, Steve McIntyre wrote: > The problem is that I don't think there's a good solution to both > problems here. We can't *know* that the system time has been read from > fake-hwclock.data before calling "save". I briefly considered adding a > "I've seen this"

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

On Mon, Mar 07, 2016 at 09:26:43AM -0300, Felipe Sateler wrote: > Excellent! I don't know how many versions you plan to keep for > stretch, if 5.6 is to be part of it, please remember to fix it there > as well. We expect to ship only one version, so hopefully 5.7 and not 5.6.

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

Hi Felipe, On Fri, Mar 04, 2016 at 04:33:20PM -0300, Felipe Sateler wrote: > It seems that the dependency is a leftover from the /run transition. > The version was dropped without explanation when updating to 5.6 from > 5.5[1], probably because the version was satisfied in stable already. >

Bug#821100: [debian-mysql] Bug#821100: MySQL 5.5.49 for Oracle April 2016 CPU

Hi Salvatore, On Mon, Apr 25, 2016 at 04:54:03PM +0200, Salvatore Bonaccorso wrote: > On Fri, Apr 22, 2016 at 09:52:44AM +0100, Robie Basak wrote: > > On Thu, Apr 21, 2016 at 07:13:34PM +0200, Salvatore Bonaccorso wrote: > > > Do you have any status-update for this for us? &

Bug#821100: [debian-mysql] Bug#821100: MySQL 5.5.49 for Oracle April 2016 CPU

On Thu, Apr 21, 2016 at 07:13:34PM +0200, Salvatore Bonaccorso wrote: > Do you have any status-update for this for us? Struggling to find an available and willing sponsor, sorry. Lars has had his tree ready for a while. I am DM for src:mysql-5.6, but not for src:mysql-5.5 (that's just a

Bug#825080: Package links against libmysqlclient_r

, and will disappear in MySQL 5.7. This change can be made now, in advance of a possible future transition to libmysqlclient20, which does not provide the _r variant. In Ubuntu, we have done this with the attached patch, which I believe is also applicable to Debian. Thanks, Robie Basak Debian MySQL

Bug#825081: Package links against libmysqlclient_r

, and will disappear in MySQL 5.7. This change can be made now, in advance of a possible future transition to libmysqlclient20, which does not provide the _r variant. In Ubuntu, we have done this with the attached quilt patch, which I believe is also applicable to Debian. Thanks, Robie Basak Debian MySQL

Bug#825077: Package links against libmysqlclient_r

, and will disappear in MySQL 5.7. This change can be made now, in advance of a possible future transition to libmysqlclient20, which does not provide the _r variant. For hhvm, we have done this in Ubuntu with the attached quilt patch, which I believe is also applicable to Debian. Thanks, Robie Basak Debian

Bug#825076: Package links against libmysqlclient_r

Basak Debian MySQL maintainers team Ubuntu developer Author: Robie Basak <robie.ba...@canonical.com> Bug-Ubuntu: https://launchpad.net/bugs/1564871 Forwarded: no Last-Update: 2016-05-20 Index: cacti-spine/configure.ac === ---

Bug#825079: Package links against libmysqlclient_r

Basak Debian MySQL maintainers team Ubuntu developer Author: Robie Basak <robie.ba...@canonical.com> Bug-Ubuntu: https://launchpad.net/bugs/1564871 Forwarded: no Last-Update: 2016-04-01 --- a/third-party/cmake/FindMySQL.cmake +++ b/third-party/cmake/FindMySQL.cmake @@ -67,7 +67,7 @@

Bug#825085: Package links against libmysqlclient_r

, Robie Basak Debian MySQL maintainers team Ubuntu developer Description: Build with mysqlclient instead of mysqlclient_r mysqlclient_r has been removed in MySQL 5.7. Since before 5.6 the two libraries have been equivalent, so can simply use mysqlclient instead Author: Lars Tangvald <lars.ta

Bug#825084: Package links against libmysqlclient_r

, and will disappear in MySQL 5.7. This change can be made now, in advance of a possible future transition to libmysqlclient20, which does not provide the _r variant. In Ubuntu, we have done this with the attached quilt patch, which I believe is also applicable to Debian. Thanks, Robie Basak Debian MySQL

Bug#825086: Package links against libmysqlclient_r

, and will disappear in MySQL 5.7. This change can be made now, in advance of a possible future transition to libmysqlclient20, which does not provide the _r variant. In Ubuntu, we have done this with the attached quilt patch, which I believe is also applicable to Debian. Thanks, Robie Basak

Bug#797260: sysbench: FTBFS: aclocal-1.14: not found

verisons of autotools +change. + + -- Robie Basak <robie.ba...@ubuntu.com> Thu, 14 Apr 2016 11:29:24 + + sysbench (0.4.12-1.1) unstable; urgency=low * Non-maintainer upload. diff -Nru sysbench-0.4.12/debian/control sysbench-0.4.12/debian/control --- sysbench-0.4.12/debian/contro

Bug#825083: Package links against libmysqlclient_r

note that this requires autoreconf so will only work if applied after my patch for bug 797260. Thanks, Robie Basak Debian MySQL maintainers team Ubuntu developer Author: Robie Basak <robie.ba...@canonical.com> Description: use libmysqlclient instead of libmysqlclient_r The former supe

Bug#831638: [debian-mysql] Bug#831638: mysql-server: mysql_install_db in postinst script does not run

tags 831638 + moreinfo thanks Hi Simon, This script has changed quite a bit recently. Please provide package version information. In mysql-5.6, I believe we use "/usr/bin/logger", which is supplied by bsdutils and is correctly declared as a dependency. In mysql-5.7 (currently in experimental),

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

On Mon, Jul 04, 2016 at 07:42:32PM +0200, Michael Biebl wrote: > Hm, that repository is gone. We unified the repository into http://anonscm.debian.org/cgit/pkg-mysql/mysql.git/log/, yesterday which does still contain the fix. > What's the state of this bug report? Seeing that 5.6 still got

Bug#853972: [debian-mysql] Bug#853972: mariadb-10.1: upgrading from mysql-5.7 renders old data inaccessible with no option to abort

Hi Julian, I'm not very keen on failing preinsts. You seem to be making an assumption that your data will still be readable after switching from MySQL to MariaDB. However, I don't make that assumption if I switch from MySQL to Postgres. One difference is that the MySQL and MariaDB packages do

Bug#853972: [debian-mysql] Bug#853972: mariadb-10.1: upgrading from mysql-5.7 renders old data inaccessible with no option to abort

On Thu, Feb 02, 2017 at 05:04:57PM +, Julian Gilbey wrote: > On Thu, Feb 02, 2017 at 04:36:02PM +0000, Robie Basak wrote: > > I think the right thing to do is the same as the MySQL->Postgres > > scenario. The data should be able to stay put. The new daemon should > > s

Bug#853008: [debian-mysql] Bug#853008: Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

Hi Julian, Thank you for reporting this. On Mon, Jan 30, 2017 at 09:24:46AM +0100, Lars Tangvald wrote: > Anyone else have any good ideas on how to handle this? I think the root cause here is that both MySQL and MariaDB packaging "own" /var/lib/mysql. This causes confusion because even though

Bug#853008: [debian-mysql] Bug#853008: Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

On Mon, Jan 30, 2017 at 10:45:44AM +0100, Lars Tangvald wrote: > I think an ok short-term solution is to make a .postrm script for > mysql-server-core, and move the delete logic there with the check on > /usr/sbin/mysqld restored, for both MariaDB and MySQL. Then we don't need to > check on any

Bug#853008: [debian-mysql] Bug#853008: Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

On Mon, Jan 30, 2017 at 06:02:30PM +, Julian Gilbey wrote: > There is an issue with this: the postrm's in mysql-server-5.7 and > mariadb-server-10.1 do significantly more than just removing > /var/lib/mysql when purging - see my (now broken because of this!) > patches on bug#852495: they also

Bug#853008: [debian-mysql] Bug#853008: Bug#853008: Bug#853008: mysql-server-5.7: purge could delete mariadb-server files with inadequate warning

On Mon, Jan 30, 2017 at 06:38:16PM +, Robie Basak wrote: > manage /var/lib/mysql manually. So perhaps it is indeed entirely > inappropriate to put purging code in the *-core package postrm. I keep saying "purging code", but what I really mean is "code that touches/d

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

Hi Otto and Julian, On Fri, Jan 27, 2017 at 02:46:39PM +0200, Otto Kekäläinen wrote: > As MariaDB and MySQL and functionally equvalent, we try to keep their > packaging identical as much as possible. If the packages divert, then > the amount of testing/maintenance increases. From a src:mysql-5.7

Bug#855892: [debian-mysql] Bug#855892: [mysql-server] more info

Ah. In that case you have a dupe of bug 850216/855935/855936. signature.asc Description: PGP signature

Bug#855892: [debian-mysql] Bug#855892: mysql-server 5.6 -> 5.7 upgrade missing mariadb.conf.d

Jason, On Wed, Feb 22, 2017 at 10:07:14PM +, Jason D Cormie wrote: > When upgrading from mysql-server 5.6 to 5.7 the installer stopped because > /etc/mysql/mariadb.conf.d didn't exist Please could you expand on this? mysql 5.7 packaging doesn't need /etc/mysql/mariadb.conf.d to exist, so we

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

On Thu, Jan 19, 2017 at 03:01:47PM +, Robie Basak wrote: > I wonder if we should have both mariadb-common and mysql-server-5.7 (ie. > everything that asks for a custom my.cnf symlink) declare a virtual > package? So add: > > Provides: mysql-my-cnf > Conflicts: mysql-m

Bug#854722: python-parallax does not depend on an ssh client

Package: python-parallax Version: 1.0.1-2 Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu zesty ubuntu-patch Dear maintainer, I just finished reviewing src:parallax for main inclusion in Ubuntu, and noticed that it doesn't depend on openssh-client. As far as I can tell,

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)

Hi Otto, On Sun, Jan 15, 2017 at 09:33:24PM +0200, Otto Kekäläinen wrote: > 2017-01-13 13:18 GMT+02:00 Robie Basak <robie.ba...@ubuntu.com>: > > So I think the configure-symlinks code needs to move from mariadb-common > > to mariadb-server-10.1 in addition. > > The Ma

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

Hi Otto, On Thu, Mar 02, 2017 at 01:04:16AM +0200, Otto Kekäläinen wrote: > Sorry for the late reply. I think that the urgent security slip was > already fixed by updating mariadb-10.1 to have the correct conflicts. I believe this is incorrect. The only commit addressing this is

Bug#855656: [debian-mysql] Bug#855656: release-notes: update on mysql/mariadb for stretch

On Sun, Feb 26, 2017 at 05:58:08PM +0100, Baptiste Jammet wrote: > I add an for the note about binary data file formats not > backwards compatible, and choose to add default-mysql-* next to > virtual-mysql-*. On Mon, Feb 27, 2017 at 10:17:18AM +1100, Vincent McIntyre wrote: > Good idea. I added

Bug#837615: [debian-mysql] Bug#837615: Don't include in stretch

On Mon, Sep 12, 2016 at 11:37:49PM +0200, Moritz Muehlenhoff wrote: > As per previous discussion, don't include in stretch/blocker bug to > keep it out. What previous discussion? I'm aware of a decision for things to depend on src:mariadb-10.0 instead, not of any decision to keep src:mysql-5.6

Bug#837615: Upload of MySQL 5.7 to unstable

Dear Release Team, I believe we're now pretty much ready for an upload of MySQL 5.7 to unstable. This would be src:mysql-5.7, which would eventually supersede src:mysql-5.6, with a general s/5.6/5.7/ in the binary package names. One significant change is the transition from libmysqlclient18 to

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

Hi Dominic, On Thu, Sep 22, 2016 at 04:10:37PM +0100, Dominic Hargreaves wrote: > > Do you have any ETA for this update being in unstable? > > I assume that there is no more work for mysql-5.6 planned by the > MySQL team, given the silence on this bug and that you are about to > upload mysql-5.7

Bug#839683: apt-key accepts short key IDs

Package: apt Version: 1.2.12~ubuntu16.04.1 I noticed this on Ubuntu, but I believe it affects Debian as well. apt-key currently accepts short key IDs. For example, https://help.ubnt.com/hc/en-us/articles/220066768 currently instructs users to run: sudo apt-key adv --keyserver

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

Hi Dominic, On Sat, Sep 24, 2016 at 01:38:19PM +0100, Dominic Hargreaves wrote: > > > 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? > > > > >

Bug#798080: Problem fixed?

fixed 798080 5.7.13-1~exp1 thanks I believe this is fixed in 5.7.13-1~exp1 in experimental, where we no longer use mysqld_safe.

Bug#843520: [debian-mysql] Bug#843520: [akonadi-server] Fails to start after mysql upgrade

On Mon, Nov 07, 2016 at 02:47:56PM +0100, Maximiliano Curia wrote: > >I think the mention of backports here was a mistake - the submitter > >specifies that the problem happened when upgrading to 5.5.53-0+deb8u1 > >which was a security update. > > Ups, it seems that I misread the version. No

Bug#843520: [debian-mysql] Bug#843520: [akonadi-server] Fails to start after mysql upgrade

On Thu, Nov 10, 2016 at 01:14:00PM +0100, Sandro Knauß wrote: > well if I understand the ERROR correctly - mysqld complains about the missing > directory /var/libs/mysql-files. Does this directory exits? It's provided by mysql-server-5.x. Since akonadi doesn't use that package (using

Bug#843520: [debian-mysql] Bug#843520: [akonadi-server] Fails to start after mysql upgrade

On Thu, Nov 10, 2016 at 02:25:59PM +0100, Sandro Knauß wrote: > > It's provided by mysql-server-5.x. Since akonadi doesn't use that > > package (using mysql-server-core-5.x directly), it's reponsible for > > creating an alternate directory inside its own structure, parallel to > > its equivalent

Bug#842011: [debian-mysql] Bug#842011: default-mysql-client forces removal of mysql-server* and mysql-client*

Hi Craig, On Tue, Oct 25, 2016 at 08:01:26PM +1100, Craig Sanders wrote: > it's somewhat surprising that a package called default-mysql-client should > force the removal of both mysql-client and mysql-server packages. Please could you explain your use case? What are you trying to do at a high

Bug#842011: [debian-mysql] Bug#842011: default-mysql-client forces removal of mysql-server* and mysql-client*

On Tue, Oct 25, 2016 at 10:00:32PM +1100, Craig Sanders wrote: > it still seems very surprising to me that a package called > default-MYSQL-client would force the removal of mysql-client* and > mysql-server* I agree this is confusing. Unfortunately we don't have a common name that describes both

Bug#842056: nmbd hangs on service start if only the loopback interface is configured

Package: samba Version: 2:4.4.6+dfsg-2 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu zesty nmbd fails to start if no interfaces are configured, even if the loopback interface _is_ configured. Steps to reproduce: apt-get update && apt-get -y install samba systemctl stop nmbd ifdown

Bug#841345: [debian-mysql] Bug#841345: mysql-server-5.7: Unable to switch from mariadb to mysql, "downgrade" is aborted

On Wed, Oct 19, 2016 at 01:49:54PM -0300, Felipe Sateler wrote: > Mariadb and mysql are supposed to be drop-in replacements, so switching > between them should be supported. This is incorrect. They aren't drop-in replacements. MariaDB changes the internal database format in ways that MySQL

Bug#841345: [debian-mysql] Bug#841345: Bug#841345: mysql-server-5.7: Unable to switch from mariadb to mysql, "downgrade" is aborted

On Wed, Oct 19, 2016 at 03:46:11PM -0300, Felipe Sateler wrote: > Then mysql and mariadb should not share the /var/lib/mysql directory, > and instead there should be a command to offer trying to "seed" the db > using the other database's files. I agree. This is my proposed solution to the problem

Bug#841592: [debian-mysql] Bug#841592: Bug#841592: Bug#841592: mysql-5.7: FTBFS: Tests failures

On Mon, Nov 14, 2016 at 12:31:43PM +0100, Lucas Nussbaum wrote: > On 14/11/16 at 02:47 -0800, Lars Tangvald wrote: > > I got it backwards, then :) > > A high number of cores might cause this if fs.aio-max-nr is set low (cat > > /proc/sys/fs/aio-max-nr | aio-nr), or rather, too low for the the >

Bug#845648: [debian-mysql] Bug#845648: mention how to deal with Pre-4.1 password hash found. It is deprecated and will be removed in a future release. Please upgrade it to a new format warning

severity 845648 minor tags 845648 + moreinfo thanks Hi Dan, On Fri, Nov 25, 2016 at 10:49:52PM +0800, 積丹尼 Dan Jacobson wrote: > Upon upgrade user sees > > Pre-4.1 password hash found. It is deprecated and will be removed in a > future release. Please upgrade it to a new format. > > This

Bug#845582: RM: mod-authnz-persona -- ROM; package will be non-functional as Mozilla are ceasing service

Package: ftp.debian.org Severity: normal Mozilla are shutting down Persona upstream: https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers The current upstream version of mod-authnz-persona will thus cease to function on 30 November, and so I don't think there's any point

Bug#844535: akonadi: akonadiserver fails to start for normal users without mysql-server-5.5 installed

tags 844535 + wontfix thanks On Thu, Nov 17, 2016 at 09:56:30AM +0100, Bálint Réczey wrote: > Control: reassign -1 mysql-5.5 5.5.53-0+deb8u1 > Control: retitle -1 mysql-server-core-5.5 should install mysql-files No, this is incorrect. The point of the mysql-server-core-* packages is to ship the

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

On Mon, Nov 21, 2016 at 11:48:56PM +1100, Matt Li wrote: > It appears that exim4 from exim4-daemon-heavy is now linked to > libmariadbclient.so.18 which does not exist in MariaDB 10.1 - only > libmysqlclient.so.18 is provided. > Where are you getting MariaDB 10.1 from? Debian currently only

Bug#843520: [debian-mysql] Bug#843520: mysql-server-5.5 cannot be automatically upgraded

Hi Jean, On Tue, Nov 15, 2016 at 12:08:18PM +0100, Jean Louis wrote: > sudo apt-get update > sudo apt-get upgrad > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > Starting or configuring mysql-server-5.5 hangs forever. System is broken. > >* What

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

Hi Otto, Note that I have a note (https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612647) about trying to keep binaries between MariaDB and MySQL synced, to try and avoid the kind of error in that bug. I don't think that is in conflict with this request at all, but it would probably be

Bug#840646: Common Breaks/Replaces fixes needed

See bug 847231 also. It should probably be fixed at the same time. signature.asc Description: PGP signature

Bug#847231: mysql Breaks/Replaces innochecksum

forcemerge 847231 847992 848118 thanks These are all the same bug. When fixing, also see bug 840646. These should all be resolved at once. signature.asc Description: PGP signature

Bug#459010: #459010 bind9 IDN support for client tools dig+host

On Tue, Aug 26, 2014 at 06:20:58PM +0200, Noël Köthe wrote: > Most of the tested clients work with IDN https://wiki.debian.org/IDN > The feature is supported in bind and just needs to be enabled: > > /tmp/bind9-9.9.5.dfsg$ ./configure --help|grep idn > --with-idn=MPREFIX enable IDN support

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)

Hi Otto, Thank you for working on this. On Fri, Jan 13, 2017 at 01:05:49AM +0200, Otto Kekäläinen wrote: > Fixed as suggested in > https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.1.git/commit/?id=75fa84af6bdf84ff95bd0cabb2a8966330d77154 I don't think this fix is sufficient. Though it may

Bug#851252: [debian-mysql] Bug#851252: mysql-server-5.7: "current start runlevel" not on boot up block the update

I don't feel that you've answered my questions. You have not provided steps to reproduce the problem. This may be a duplicate of bug 843959 (LP: #1592669) but I am not sure. signature.asc Description: PGP signature

Bug#851252: [debian-mysql] Bug#851252: mysql-server-5.7: "current start runlevel" not on boot up block the update

tags 851252 + moreinfo thanks Hi Daniele, I'm not sure why you've filed this bug in Debian. Should it not be on Launchpad as you're running an Ubuntu system? Or have you verified that this issue affects Debian also? On Fri, Jan 13, 2017 at 12:56:32PM +0100, Daniele Scasciafratte wrote: > I have

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

On Thu, Jan 12, 2017 at 03:18:17PM +0100, Norvald H. Ryeng wrote: > On Thu, 12 Jan 2017 13:16:32 +0100 > Dominik George wrote: > > Their claim that mariadb can > > simply be used as a drop-in replacement does not hold true... > The

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

reassign 850216 libmariadbclient18 thanks Hi Salvatore, Thank you for the report. I can reproduce this on stretch. Otto: please could you take a look at this? It seems that the problem is that libmariadbclient18 depends on mariadb-common directly. mariadb-common's postinst adds

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

severity 848914 wishlist tags 848914 + help thanks Hi, On Tue, Dec 20, 2016 at 02:07:22PM -0500, westlake wrote: > please add support for /etc/default/mysql-server, otherwise users would need > to edit script files in order to pass custom command-line arguments Our focus is on the systemd

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

On Tue, Dec 20, 2016 at 03:06:58PM -0500, westlake wrote: > I looked at it again and solved it.. OK. I guess I can leave this open though, since it's a reasonable request for the init.d script. > I could not tell whether systemd was using /etc/init.d/mysql or an actual > unit file so perhaps

Bug#858457: spamd stops autostarting after release upgrade

Package: spamassassin Version: 3.4.0-6 User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-units X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org If in wheezy I enable spamd by setting ENABLED=1 in /etc/default/spamassassin, and then I upgrade to jessie, then

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

Hi Otto, On Fri, Mar 10, 2017 at 05:09:42PM +0200, Otto Kekäläinen wrote: > I wonder if this really is how update-alternatives should be used and > is really adding conflicts between all packages that use it the smart > way to utilize the flexibility the update-alternatives scheme should >

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

On Wed, Mar 08, 2017 at 11:00:35PM +0200, Otto Kekäläinen wrote: > I am not sure what the actual problem here is. What are you trying to > achieve which does not work? I think pkgconfig and mysql_config from libmariadbclient-dev should be specifying -lmariadbclient instead of -lmysqlclient. I

<    1   2   3   4   >