[debian-mysql] mysql-5.7: secure_file_priv

[Clint Byrum]

Excerpts from Norvald H. Ryeng's message of 2016-01-12 07:39:30 -0800:
> On Tue, 12 Jan 2016 16:18:33 +0100, Bjoern Boschman <bjoern at boschman.de>  
> wrote:
> 
> > Hi folks,
> >
> > I think we both have the same understanding of the manual :-)
> > My point about secure_file_priv is that users comming from mysql-5.6 or
> > smaller which already are using operations like 'LOAD DATA INFILE..' now
> > will be confused, as they might not know this new security feature.
> > But this could/should be handled via NEWS.Debian
> >
> > Anyhow i've pushed my latest work into git with the following problem:
> >
> > mysql-5.7 clean install works.
> >
> > mysql-5.5 -> mysql-5.7
> > mysql-5.6 -> mysql-5.7
> >   still some failures due to changed upgradepath
> >   I still have not figured out how to implement a rubust mysql_upgrade
> > during upgrade.
> >
> > @ora: I know that your documentation states that "Direct upgrades that  
> > skip
> > a release level (for example, upgrading directly from MySQL 5.5 to 5.7)  
> > are
> > not recommended or supported"
> > Anyhow - we still got several month before stretch will be freezed and  
> > I'd
> > really would like to ship mysql-5.7 already?
> > What do you folks think about?
> 
> I agree, we should go for a direct 5.5->5.7 upgrade.
> 

Is that a supported operation? If not, then IMO, we cannot ship 5.7
until 5.6 has shipped in a stable release.