Re: mysql/percona/maria...

[Tomasz Pala]

On Sat, Oct 29, 2016 at 11:46:26 +0200, Jacek Konieczny wrote:

> That (nameXY) would be more usefull for PostgreSQL, where old and new
> version need to be installed for a database upgrade between different
> major versions.

Hm? Actually never did that for years...

"pg_upgrade supports upgrades from 8.4.X and later to the current major
release of PostgreSQL, including snapshot and alpha releases."


What does require old version, and not just the previous one, but EVERY
one in-between, is ownCloud:

"Make sure that you dont skip a major release when upgrading via
repositories. For example you cant upgrade from 8.1.x to 9.0.x directly
as you would skip the 8.2.x major release"

-- 
Tomasz Pala 
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: mysql/percona/maria...

[Jacek Konieczny]

On 2016-10-29 11:17, Arkadiusz Miśkiewicz wrote:
> On Saturday 29 of October 2016, Elan Ruusamäe wrote:
>> On 29.10.2016 11:25, Elan Ruusamäe wrote:
>>> should we introduce mysql57, mysql80 packages instead?
> 
> Only if there are incompatible on upgrade path. To be verified with docs. 
> Otherwise all versions as mysql package.

That (nameXY) would be more usefull for PostgreSQL, where old and new
version need to be installed for a database upgrade between different
major versions. Currently PostgreSQL upgrade in PLD is a problem.
Though, I am not sure doing it right and maintaining later is worth the
effort for our tiny team.

>> here's some idea:
>>
>> 1. make percona-server.spec:5.7 clean upgrade path from mysql.spec:5.6
>> 2. do not build mysql.spec officially at all
>> 3. build system tools using percona-server-devel via "Provides:
>> mysql-devel" 4. mariadb - ship it only if it does not conflict with
>> mysql-libs or mysql-devel
> 
> Sounds good to me.
> 
> (I would switch entire distribution to mariadb though (but keep percona 
> server 
> package, too)

Sound goot to me to. It seems other distributions do similarily –
mariadb is used instead of Oracle mysql and no non-Oracle mysql fork is
packaged as 'mysql'.

Jacek
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: mysql/percona/maria...

[Arkadiusz Miśkiewicz]

On Saturday 29 of October 2016, Elan Ruusamäe wrote:
> On 29.10.2016 11:25, Elan Ruusamäe wrote:
> > hi
> > 
> > how is it planned to handle that mysql.spec is now different product
> > (mysql vs percona)
> > and all those mariadb and percona-server packages.
> > 
> > mysql 5.6 -> 5.7 MAY NOT be upgraded automatically. 

Here oracle 5.7 started fine with percona 5.6 db files but you are probably 
right and in some cases it won't work.

> > if someone used
> > features from percona-server 5.6 that are now not present in
> > mysql-community version in mysql.spec 5.7 their systems would be BROKEN.
> > 
> > some idea: rename mysql.spec to mysql-community.spec ?
> > 
> > should we introduce mysql57, mysql80 packages instead?

Only if there are incompatible on upgrade path. To be verified with docs. 
Otherwise all versions as mysql package.

> > 
> > ps: fedora has their mysql named as community-mysql.spec
> 
> here's some idea:
> 
> 1. make percona-server.spec:5.7 clean upgrade path from mysql.spec:5.6
> 2. do not build mysql.spec officially at all
> 3. build system tools using percona-server-devel via "Provides:
> mysql-devel" 4. mariadb - ship it only if it does not conflict with
> mysql-libs or mysql-devel

Sounds good to me.

(I would switch entire distribution to mariadb though (but keep percona server 
package, too)

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: mysql/percona/maria...

[Elan Ruusamäe]

On 29.10.2016 11:25, Elan Ruusamäe wrote:

hi

how is it planned to handle that mysql.spec is now different product 
(mysql vs percona)

and all those mariadb and percona-server packages.

mysql 5.6 -> 5.7 MAY NOT be upgraded automatically. if someone used 
features from percona-server 5.6 that are now not present in 
mysql-community version in mysql.spec 5.7 their systems would be BROKEN.


some idea: rename mysql.spec to mysql-community.spec ?

should we introduce mysql57, mysql80 packages instead?

ps: fedora has their mysql named as community-mysql.spec


here's some idea:

1. make percona-server.spec:5.7 clean upgrade path from mysql.spec:5.6
2. do not build mysql.spec officially at all
3. build system tools using percona-server-devel via "Provides: mysql-devel"
4. mariadb - ship it only if it does not conflict with mysql-libs or 
mysql-devel



--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

mysql/percona/maria...

[Elan Ruusamäe]

hi

how is it planned to handle that mysql.spec is now different product 
(mysql vs percona)

and all those mariadb and percona-server packages.

mysql 5.6 -> 5.7 MAY NOT be upgraded automatically. if someone used 
features from percona-server 5.6 that are now not present in 
mysql-community version in mysql.spec 5.7 their systems would be BROKEN.


some idea: rename mysql.spec to mysql-community.spec ?

should we introduce mysql57, mysql80 packages instead?

ps: fedora has their mysql named as community-mysql.spec

--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en