search

phpbb / epv

Extension Pre-Validator
GNU General Public License v2.0
9 stars 17 forks source link

Support Symfony 3 / phpBB master branch #50

Closed iMattPro closed 7 years ago

iMattPro commented 8 years ago

Tests using EPV in phpBB master branch fail because phpBB 3.3 uses Symfony 3.x... EPV is on Symfony 2.x.

https://travis-ci.org/VSEphpbb/abbc3/jobs/156994287#L801

Problem 1
    - Installation request for phpbb/epv dev-master -> satisfiable by phpbb/epv[dev-master].
    - phpbb/epv dev-master requires symfony/yaml ~2.3 -> satisfiable by symfony/yaml[2.3.x-dev, 2.4.x-dev, 2.5.x-dev, 2.6.x-dev, 2.7.x-dev, 2.8.x-dev, v2.3.0, v2.3.1, v2.3.10, v2.3.11, v2.3.12, v2.3.13, v2.3.14, v2.3.15, v2.3.16, v2.3.17, v2.3.18, v2.3.19, v2.3.2, v2.3.20, v2.3.21, v2.3.22, v2.3.23, v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.3, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.3.38, v2.3.39, v2.3.4, v2.3.40, v2.3.41, v2.3.42, v2.3.5, v2.3.6, v2.3.7, v2.3.8, v2.3.9, v2.4.0, v2.4.0-BETA1, v2.4.0-BETA2, v2.4.0-RC1, v2.4.1, v2.4.10, v2.4.2, v2.4.3, v2.4.4, v2.4.5, v2.4.6, v2.4.7, v2.4.8, v2.4.9, v2.5.0, v2.5.0-BETA1, v2.5.0-BETA2, v2.5.0-RC1, v2.5.1, v2.5.10, v2.5.11, v2.5.12, v2.5.2, v2.5.3, v2.5.4, v2.5.5, v2.5.6, v2.5.7, v2.5.8, v2.5.9, v2.6.0, v2.6.0-BETA1, v2.6.0-BETA2, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.0-BETA1, v2.7.0-BETA2, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.2, v2.8.3, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9] 
but these conflict with your requirements or minimum-stability.
iMattPro commented 7 years ago

bump

DavidIQ commented 7 years ago

Do we need to worry about this right now? I can't really think of a way we could fix this without breaking tests for 3.1 and 3.2 other than creating separate branches. If that's not the way to go then suggestions welcome.

iMattPro commented 7 years ago

SHouldn't break anything. Just needs to updates it's own symfony component versions. All of the dependencies could use updating, some are very very old.

iMattPro commented 7 years ago

Separate branches shouldn't be a problem, if this will in fact not be compatible with 3.1, 3.2. Either way, this will need to work for 3.3 and 3.2 anyways, so a solution of some kind is needed.