Bug#793316: transition: mysql-5.6

2015-07-23 Thread Robie Basak
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 never agreed. I'm looking after the mysql-* packaging at the

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

2015-09-14 Thread Robie Basak
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#793316: [debian-mysql] Bug#793316: transition: mysql-5.6

2015-09-18 Thread Robie Basak
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

Request for release team decision on MySQL and MariaDB [was: Re: Bug#793316: [debian-mysql] Bug#793316: transition: mysql-5.6]

2015-12-14 Thread Robie Basak
Hi Jonathan, Dropping the bug from this thread since that bug is done and adding the general debian-release list instead. I think that a release team decision is still outstanding. The background is archived at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793316. On Wed, Sep 16, 2015 at

Re: Request for release team decision on MySQL and MariaDB [was: Re: Bug#793316: [debian-mysql] Bug#793316: transition: mysql-5.6]

2015-12-18 Thread Robie Basak
(removing Jonathan specifically; the debian-release ML should be sufficient as this is for the release team generally now) On Mon, Dec 14, 2015 at 05:45:24PM +, Robie Basak wrote: > Can I ask that this request (for the release team to make a decision > between the choices I outl

Re: Request for release team decision on MySQL and MariaDB [was: Re: Bug#793316: [debian-mysql] Bug#793316: transition: mysql-5.6]

2016-01-11 Thread Robie Basak
On Mon, Jan 11, 2016 at 08:13:56PM +0100, Salvatore Bonaccorso wrote: > > MySQL is maintained in jessie. What makes you think it's not? > > My gut feeling is that this is not true, I'm sorry. All recent updates > were prepared by the security team itself due to this. And most of > the recent

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

2016-06-24 Thread Robie Basak
On Wed, Jun 01, 2016 at 07:03:42PM +0200, Andreas Beckmann wrote: > I prepared a prototype for a separate mysql-common package (and > default-* packages) at > git://git.debian.org/git/users/anbe/tmp/mysql-defaults.git > but so far nobody had time to review it. A thought from Norvald. Do we really

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

2016-06-24 Thread Robie Basak
On Fri, Jun 24, 2016 at 07:53:56PM +0200, Julien Cristau wrote: > Please don't use virtual-foo for non-virtual packages, that way lies > madness and confusion and despair :) OK, but does anyone have any objection to the principle of my suggestion, even if we must use a different name?

Re: [debian-mysql] Request for release team decision on MySQL and MariaDB [was: Re: Bug#793316: Bug#793316: transition: mysql-5.6]

2016-01-11 Thread Robie Basak
On Mon, Jan 11, 2016 at 02:52:26PM +0100, Pedretti Fabio wrote: > Note however that for other debian packaged softwares a choice was made, > here are some I just remember: > - openoffice / libreoffice > - xfree86 / xorg > - libav / ffmpeg This is a valid point, but is the situation really

Re: Request for release team decision on MySQL and MariaDB [was: Re: Bug#793316: [debian-mysql] Bug#793316: transition: mysql-5.6]

2016-01-11 Thread Robie Basak
On Mon, Jan 11, 2016 at 07:27:30PM +0100, Moritz Mühlenhoff wrote: > *Sigh*. And that is exactly the problem (and we've already pointed this > out at DebConf half a year ago) > > We should really go ahead and move forward, the freeze isn't terribly far > away. I don't think it's reasonable to

Re: Request for release team decision on MySQL and MariaDB [was: Re: Bug#793316: [debian-mysql] Bug#793316: transition: mysql-5.6]

2016-01-15 Thread Robie Basak
On Thu, Jan 14, 2016 at 10:11:22PM +0100, Moritz Mühlenhoff wrote: > This is EOD from my side. This has all been discussed to death and > I won't spend further time on this. I agree that this has come up many times, but no, this has not been discussed to death. Every time it comes up, all we ever

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

2016-01-27 Thread Robie Basak
Hi Niels, Thank you for your considered response. On Tue, Jan 26, 2016 at 11:50:08PM +, Niels Thykier wrote: > I do not feel the listed options accurately reflect the issues / > concerns in play. As *I see it*, these are the options: > > 1) Default to MySQL with MariaDB also available

Re: [debian-mysql] [Summary] Request for release team decision on MySQL and MariaDB

2016-01-27 Thread Robie Basak
the ABI is different and according to > investigations by Robie Basak going back September 2014 [1] the > upgrade might break something, and while it is now partially remedied, > the ABI bump has never been done, the symbols file to track this all > is missing from the packaging, and th

[Summary] Request for release team decision on MySQL and MariaDB

2016-01-25 Thread Robie Basak
In this summary I make no new arguments. I only summarise what has already been said and provide references to back up what has already been said. References are in the form [-MM-DD] or [-MM-DD-X] where disambiguation is needed. URLs are at the bottom. Where I have not used quotes, I am

Re: Request for release team decision on MySQL and MariaDB

2016-01-25 Thread Robie Basak
On Mon, Jan 25, 2016 at 10:14:01PM +, Robie Basak wrote: > I will send a separate email about what I propose we do next. In this > email, I'm sticking to the historical record of facts already raised so > that we can all refer to it. I hope that the summary is useful and that I

Re: [debian-mysql] About packages that depend on mysql-* / mariadb / virtual-mysql-*

2016-07-05 Thread Robie Basak
On Tue, Jul 05, 2016 at 11:41:15AM +0200, Jonathan Wiltshire wrote: > > I suggest we extend the mysql-defaults source package to provide a > > real default-mysqlclient-dev metapackage, which other packages can > > build depend on, using versions if needed (just as default-jdk does). > > Yes. > >

Upload of MySQL 5.7 to unstable

2016-09-21 Thread Robie Basak
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

Re: [debian-mysql] Fixing the jessie->stretch upgrade path

2017-05-12 Thread Robie Basak
Hi Ondřej, Thank you for working on this. On Fri, May 12, 2017 at 11:26:13AM +0200, Ondřej Surý wrote: > Therefore I am proposing a one time fix specifically targeted at > stretch. I would like to prepare 'mysql-transitional' package that will > create a couple of dummy/transitional packages

Bug#925576: unblock: python-trustme/0.4.0-2

2019-04-02 Thread Robie Basak
Hi Paul, On Sun, Mar 31, 2019 at 10:40:38AM +0200, Paul Gevers wrote: > The fix doesn't prevent the package from FTBFS. Please check > https://buildd.debian.org/status/fetch.php?pkg=python-trustme=all=0.4.0-2=1553646768=0 Thanks. I only spotted that after you approved the unblock request. It did

Bug#925576: unblock: python-trustme/0.4.0-2

2019-03-26 Thread Robie Basak
/changelog 2019-03-26 23:23:50.0 + @@ -1,3 +1,10 @@ +python-trustme (0.4.0-2) unstable; urgency=medium + + * Explicitly build-depend on python3-idna to fix FTBFS. +Closes: #925566. + + -- Robie Basak Tue, 26 Mar 2019 23:22:42 + + python-trustme (0.4.0-1) unstable; urgency

Bug#927118: unblock: python-trustme/0.4.0-3

2019-04-15 Thread Robie Basak
. This fixes another FTBFS due to test failure in the case that +the openssl binary package is installed, which is not a build dependency, +but apparently the buildds have it by default. Closes: #926652. + + -- Robie Basak Sat, 13 Apr 2019 17:30:20 +0100 + +python-trustme (0.4.0-2) unstable

Bug#968356: transition: mysql-8.0

2020-08-13 Thread Robie Basak
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Though this is a transition, I don't think it requires the usual coordination with the release team because it won't entangle with anything. src:mysql-5.7 generates binary package