[debian-mysql] Processing of mysql-5.6_5.6.34-1_source.changes

[Dominic Hargreaves]

On Tue, Nov 08, 2016 at 04:27:52PM +0000, Robie Basak wrote:
> On Tue, Nov 08, 2016 at 02:50:45PM +0000, Debian FTP Masters wrote:
> > mysql-5.6_5.6.34-1_source.changes uploaded successfully to localhost
> > along with the files:
> >   mysql-5.6_5.6.34-1.dsc
> >   mysql-5.6_5.6.34.orig.tar.gz
> >   mysql-5.6_5.6.34-1.debian.tar.xz
> 
> I don't understand why this was done. mysql-5.6 is slated for removal
> from testing, and mysql-5.7 supersedes it. We're already shipping 5.7
> versions of the binaries mysql-server, libmysqlclient-dev, and so on in
> unstable. But you've just uploaded 5.6 version takeovers of these binary
> packages, no?

Hi,

That upload is a result of the plan discussed at the thread
starting at
<http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2016-October/009602.html> where I explained why I thought it was appropriate - in brief - to
support a minimally-invasive security update to jessie-backports. But
even though mysql-common was removed from that package, I overlooked
the other non-versioned package names, and I'm sorry for that.

I think that the archive will reject those binary packages because of the
lower version number, so the damage may not be too large?

I was just in the process of preparing a sponsored upload of MySQL 5.7
in response to Lars' request here:

http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2016-November/009750.html

but it's probably better to wait and see what happens with the MySQL
5.6 upload before doing that. If the wrong versions of those shared
packages do make it to the archive, they can be replaced by a subsequent
upgrade of MySQL 5.7.

Since you mentioned testing - my understanding is that mysql-5.7 won't
enter testing either, so I don't think that this mishap affects the 
release. But then again, there is no release team RC bug, which I
thought there was, so maybe I'm wrong on that front too..

Thanks,
Dominic.