{"action":"created","issue":{"url":"https://api.github.com/repos/oroinc/orocommerce/issues/64","repository_url":"https://api.github.com/repos/oroinc/orocommerce","labels_url":"https://api.github.com/repos/oroinc/orocommerce/issues/64/labels{/name}","comments_url":"https://api.github.com/repos/oroinc/orocommerce/issues/64/comments","events_url":"https://api.github.com/repos/oroinc/orocommerce/issues/64/events","html_url":"https://github.com/oroinc/orocommerce/issues/64","id":294615764,"number":64,"title":"\"composer update\" fails for OroCommerce 1.6 application","user":{"login":"aligentjim","id":1243412,"avatar_url":"https://avatars3.githubusercontent.com/u/1243412?v=4","gravatar_id":"","url":"https://api.github.com/users/aligentjim","html_url":"https://github.com/aligentjim","followers_url":"https://api.github.com/users/aligentjim/followers","following_url":"https://api.github.com/users/aligentjim/following{/other_user}","gists_url":"https://api.github.com/users/aligentjim/gists{/gist_id}","starred_url":"https://api.github.com/users/aligentjim/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aligentjim/subscriptions","organizations_url":"https://api.github.com/users/aligentjim/orgs","repos_url":"https://api.github.com/users/aligentjim/repos","events_url":"https://api.github.com/users/aligentjim/events{/privacy}","received_events_url":"https://api.github.com/users/aligentjim/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-02-06T02:57:30Z","updated_at":"2018-02-06T13:59:17Z","closed_at":"2018-02-06T11:12:10Z","author_association":"NONE","body":"Using an unmodified version of the orocommerce-application repository I'm unable to run \"composer update\" due to dependency errors (see below).  We've also seen the same issue on an existing 1.5 install that we're upgrading to 1.6.  In that case our normal procedure would be to merge changes in `composer.json` and run `composer update` to fix the `composer.lock` file.  \r\n\r\nIt looks like the \"out of the box\" composer.json requires a set of packages which is no longer installable.\r\n\r\nThe composer output is shown below...\r\n\r\n```\r\n$ composer update --no-dev -v\r\nVESSEL: vessel user will have id: 775000001\r\nLoading composer repositories with package information\r\nUpdating dependencies\r\nDependency resolution completed in 109.278 seconds\r\nYour requirements could not be resolved to an installable set of packages.\r\n\r\n  Problem 1\r\n    - Conclusion: don't install phpunit/phpunit 5.7.27\r\n    - Conclusion: remove phpunit/phpunit 5.7.26\r\n    - Conclusion: don't install phpunit/phpunit 5.7.26\r\n    - Conclusion: don't install phpunit/phpunit 5.7.25\r\n    - Conclusion: don't install phpunit/phpunit 5.7.24\r\n    - Conclusion: don't install phpunit/phpunit 5.7.23\r\n    - Conclusion: don't install phpunit/phpunit 5.7.22\r\n    - Conclusion: don't install phpunit/phpunit 5.7.21\r\n    - Conclusion: don't install phpunit/phpunit 5.7.20\r\n    - Conclusion: don't install phpunit/phpunit 5.7.19\r\n    - Conclusion: don't install phpunit/phpunit 5.7.18\r\n    - Conclusion: don't install phpunit/phpunit 5.7.17\r\n    - Conclusion: don't install phpunit/phpunit 5.7.16\r\n    - Conclusion: don't install phpunit/phpunit 5.7.15\r\n    - Conclusion: don't install phpunit/phpunit 5.7.14\r\n    - Conclusion: don't install phpunit/phpunit 5.7.13\r\n    - Conclusion: don't install phpunit/phpunit 5.7.12\r\n    - Conclusion: don't install phpunit/phpunit 5.7.11\r\n    - Conclusion: don't install phpunit/phpunit 5.7.10\r\n    - Conclusion: don't install phpunit/phpunit 5.7.9\r\n    - Conclusion: don't install phpunit/phpunit 5.7.8\r\n    - Conclusion: don't install phpunit/phpunit 5.7.7\r\n    - Conclusion: don't install phpunit/phpunit 5.7.6\r\n    - Conclusion: don't install phpunit/phpunit 5.7.5\r\n    - Conclusion: don't install phpunit/phpunit 5.7.4\r\n    - Conclusion: don't install phpunit/phpunit 5.7.3\r\n    - Conclusion: don't install phpunit/phpunit 5.7.2\r\n    - Conclusion: don't install phpunit/phpunit 5.7.1\r\n    - Conclusion: don't install phpunit/phpunit 5.7.0\r\n    - Conclusion: remove phpunit/php-timer 1.0.9\r\n    - Installation request for phpunit/phpunit 5.7.* -> satisfiable by phpunit/phpunit[5.7.0, 5.7.1, 5.7.10, 5.7.11, 5.7.12, 5.7.13, 5.7.14, 5.7.15, 5.7.16, 5.7.17, 5.7.18, 5.7.19, 5.7.2, 5.7.20, 5.7.21, 5.7.22, 5.7.23, 5.7.24, 5.7.25, 5.7.26, 5.7.27, 5.7.3, 5.7.4, 5.7.5, 5.7.6, 5.7.7, 5.7.8, 5.7.9, 5.7.x-dev].\r\n    - Conclusion: remove sebastian/phpcpd dev-master\r\n    - sebastian/phpcpd dev-master requires phpunit/php-timer ^2.0 -> satisfiable by phpunit/php-timer[2.0.0, 2.0.x-dev].\r\n    - Can only install one of: phpunit/php-timer[2.0.0, 1.0.x-dev].\r\n    - Can only install one of: phpunit/php-timer[2.0.x-dev, 1.0.x-dev].\r\n    - phpunit/phpunit 5.7.x-dev requires phpunit/php-timer ^1.0.6 -> satisfiable by phpunit/php-timer[1.0.9, 1.0.6, 1.0.7, 1.0.8, 1.0.x-dev].\r\n    - Conclusion: don't install phpunit/php-timer 1.0.9|don't install sebastian/phpcpd dev-master\r\n    - Conclusion: don't install phpunit/php-timer 1.0.8|don't install sebastian/phpcpd dev-master\r\n    - Conclusion: don't install phpunit/php-timer 1.0.7|don't install sebastian/phpcpd dev-master\r\n    - Conclusion: don't install phpunit/php-timer 1.0.6|don't install sebastian/phpcpd dev-master\r\n    - Installation request for sebastian/phpcpd dev-master#cff7f36c2ae89d59987de25d14fd41a72dd4a703 as 3.1.0 -> satisfiable by sebastian/phpcpd[dev-master].\r\n\r\nRunning update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.\r\n\r\n```"},"comment":{"url":"https://api.github.com/repos/oroinc/orocommerce/issues/comments/363429977","html_url":"https://github.com/oroinc/orocommerce/issues/64#issuecomment-363429977","issue_url":"https://api.github.com/repos/oroinc/orocommerce/issues/64","id":363429977,"user":{"login":"aivus","id":1021703,"avatar_url":"https://avatars1.githubusercontent.com/u/1021703?v=4","gravatar_id":"","url":"https://api.github.com/users/aivus","html_url":"https://github.com/aivus","followers_url":"https://api.github.com/users/aivus/followers","following_url":"https://api.github.com/users/aivus/following{/other_user}","gists_url":"https://api.github.com/users/aivus/gists{/gist_id}","starred_url":"https://api.github.com/users/aivus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aivus/subscriptions","organizations_url":"https://api.github.com/users/aivus/orgs","repos_url":"https://api.github.com/users/aivus/repos","events_url":"https://api.github.com/users/aivus/events{/privacy}","received_events_url":"https://api.github.com/users/aivus/received_events","type":"User","site_admin":false},"created_at":"2018-02-06T13:59:17Z","updated_at":"2018-02-06T13:59:17Z","author_association":"MEMBER","body":"Hi @alexbaat \r\n\r\nFix should be released in the next patch version (1.6.1)"}}
{"actor":{"display_login":"aivus"}}