SilverStripe 3.0 upgrade to 3.1 failure with Composer -
i've never upgraded silverstripe project before, forgive me if i'm missing obvious.
i want upgrade 3.0.5 silverstripe site have running locally latest version (which 3.1.6 or similar). updated composer.json file (which located within project in [project name]/cms/composer.json) such:
{ "name": "silverstripe/cms", "type": "silverstripe-module", "description": "the silverstripe content management system", "homepage": "http://silverstripe.org", "license": "bsd-3-clause", "keywords": ["silverstripe", "cms"], "authors": [ { "name": "silverstripe", "homepage": "http://silverstripe.com" }, { "name": "the silverstripe community", "homepage": "http://silverstripe.org" } ], "require": { "php": ">=5.3.2", "composer/installers": "*", "silverstripe/cms": "3.1.*", "silverstripe/framework": "3.1.*" }, "autoload": { "classmap": ["tests/behat/"] }
}
i updated composer prompted in terminal.
i went composer.json file located, ran composer update in terminal , got error:
loading composer repositories package information updating dependencies (including require-dev) requirements not resolved installable set of packages. problem 1 - can install 1 of: silverstripe/cms[3.1.0, dev-master]. - can install 1 of: silverstripe/cms[3.1.1, dev-master]. - can install 1 of: silverstripe/cms[3.1.10, dev-master]. - can install 1 of: silverstripe/cms[3.1.11, dev-master]. - can install 1 of: silverstripe/cms[3.1.12, dev-master]. - can install 1 of: silverstripe/cms[3.1.13, dev-master]. - can install 1 of: silverstripe/cms[3.1.14, dev-master]. - can install 1 of: silverstripe/cms[3.1.15, dev-master]. - can install 1 of: silverstripe/cms[3.1.2, dev-master]. - can install 1 of: silverstripe/cms[3.1.3, dev-master]. - can install 1 of: silverstripe/cms[3.1.4, dev-master]. - can install 1 of: silverstripe/cms[3.1.5, dev-master]. - can install 1 of: silverstripe/cms[3.1.6, dev-master]. - can install 1 of: silverstripe/cms[3.1.7, dev-master]. - can install 1 of: silverstripe/cms[3.1.8, dev-master]. - can install 1 of: silverstripe/cms[3.1.9, dev-master]. - installation request silverstripe/cms dev-master -> satisfiable silverstripe/cms[dev-master]. - installation request silverstripe/cms 3.1.* -> satisfiable silverstripe/cms[3.1.0, 3.1.1, 3.1.10, 3.1.11, 3.1.12, 3.1.13, 3.1.14, 3.1.15, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.1.7, 3.1.8, 3.1.9].
do need specific version of silverstripe need update to? didn't see composer.lock file in project, did remove line in web.config calling one:
<add segment="composer.lock" />
should composer.json file located elsewhere in project (as opposed [project name]/cms)?
update: composer installed in root directory , composure.json file located there, still errors when trying upgrade site silverstripe 3.1:
composer update loading composer repositories package information updating dependencies (including require-dev) - updating composer/installers dev-master (v1.0.2 => e420b53) [runtimeexception] .git directory missing /projects/[project name]/vendor/composer/installers, see https://getcomposer.org/commit-deps more information update [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--lock] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--with-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [packages1] ... [packagesn] ~/projects/[project name] $ php composer.phar install loading composer repositories package information installing dependencies (including require-dev) - updating silverstripe/framework (3.0.x-dev 29de643 => 3.1.x-dev 92970f8) [runtimeexception] .git directory missing framework/, see https://getcomposer.org/commit-deps more information install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--ignore-platform-reqs] [packages1] ... [packagesn]
you shouldn’t editing cms/composer.json, should editing composer.json @ root of project (if there 1 present - there may not composer.json if previous developer didn't install composer).
Comments
Post a Comment