On Fri, May 25, 2012 at 00:35:45 -0700, Clint Byrum wrote:
I've done some testing on this. The piece of my.cnf that I thought
would break client and libmysqlclient does not. It only breaks
mysql-server-core-5.1:
120525 0:20:34 [ERROR] mysqld: unknown variable
Clint Byrum cl...@ubuntu.com (25/05/2012):
I've done some testing on this. The piece of my.cnf that I thought
would break client and libmysqlclient does not. It only breaks
mysql-server-core-5.1:
120525 0:20:34 [ERROR] mysqld: unknown variable
'lc-messages-dir=/usr/share/mysql'
So the
Excerpts from Adam D. Barratt's message of Sat May 19 08:51:34 -0700 2012:
On Tue, 2012-05-08 at 06:18 -0700, Clint Byrum wrote:
On May 8, 2012, at 2:04, Julien Cristau jcris...@debian.org wrote:
On Tue, May 1, 2012 at 22:52:22 +0100, Nicholas Bamber wrote:
At some point we need to
On Mon, May 21, 2012 at 11:34:16 -0700, Clint Byrum wrote:
For anything critical like the PHP update, would it be prudent to upload
a new one with the build dependency bumped back to libmysqlclient16-dev
so they can progress to testing independent of this transition?
There's no such thing as
Excerpts from Adam D. Barratt's message of Sat May 19 08:51:34 -0700 2012:
On Tue, 2012-05-08 at 06:18 -0700, Clint Byrum wrote:
On May 8, 2012, at 2:04, Julien Cristau jcris...@debian.org wrote:
On Tue, May 1, 2012 at 22:52:22 +0100, Nicholas Bamber wrote:
At some point we need to
On Mon, May 21, 2012 at 11:34:16 -0700, Clint Byrum wrote:
mysql-common 5.5 will break 5.1 because there are new configuration
options used in /etc/mysql/my.cnf that will *break* mysql 5.1, as in,
it will refuse to run, libmysqlclient will throw errors, etc. This is
an unfortunate, but
On Tue, 2012-05-08 at 06:18 -0700, Clint Byrum wrote:
On May 8, 2012, at 2:04, Julien Cristau jcris...@debian.org wrote:
On Tue, May 1, 2012 at 22:52:22 +0100, Nicholas Bamber wrote:
At some point we need to transition from mysql-5.1 to mysql-5.5. We
would like to do this before the freeze
On Tue, May 8, 2012 at 11:04 AM, Julien Cristau jcris...@debian.org wrote:
If that fails then we will be left supporting a version of MySQL that is not
supported upstream.
Given how well that support works anyway I'm not sure how much of a
loss that is.
(AFAIK:)
Debian-style minimal security
On May 8, 2012, at 2:04, Julien Cristau jcris...@debian.org wrote:
On Tue, May 1, 2012 at 22:52:22 +0100, Nicholas Bamber wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
At some point we need to transition from
Julien,
I am sorry. I got into a panic state over getting rid of mysql-5.1. In
hindsight I can see that there were betters ways of getting the
attention of the release team. I am trying to do the right thing.
On 08/05/12 10:04, Julien Cristau wrote:
On Tue, May 1, 2012 at 22:52:22 +0100,
I think those are defensible although I take the point that the
changelog is misleading. For example we just stripped out a lot of stuff
that used procps and the upstream move to cmake removed a lot of
explicit build dependencies so it was natural to ask whether these are
still required. I
11 matches
Mail list logo
