Composer install issue on prod, no issues on local enviroment - php

Recently I unignored composer.lock along with package-lock.json (likely unrelated), and I changed our gulp deploy script to use composer install instead of composer update. Before pushing new code to prod servers I updated the lock files to the latest using composer update and npm update to make sure there was nothing weird in there from branch merges.
However the gulp deployment script hit various issues, the most problematic of which was: "Requirements could not be resolved to an installable set of packages"
gulp-tasks/deploy.js in its current state:
var args = require('yargs').argv;
var exec = require('./helpers/exec');
var runSequence = require('run-sequence');
module.exports = function (gulp, plugins, settings) {
return function (completed) {
var jsBundle = [];
// Set production / staging only bundling options
settings.env === 'production' || settings.env === 'staging'
? jsBundle.push('js:bundle-production')
: jsBundle.push('js:bundle-vendor', 'js:bundle-vue', 'js:bundle-core');
if (!args.x) { // Exclude mode
console.log('Fetching latest commits from remote repository..');
exec('git fetch');
try {
console.log('Attempting to merge upstream branch into local..');
exec('git merge'); // If up-stream set on branch, merge it into local branch
} catch (e) {}
}
if (args.v) { // Checkout version tag
console.log('Checking out release tag..');
exec('git checkout tags/' + args.v);
}
if (args.s) { // Speed mode
console.log('Building JS and SASS..');
runSequence(
'make:htaccess',
'sass:compile',
'js:bundle-login',
jsBundle,
'copy-public',
'remove:config',
completed
);
} else if (args.b) {
runSequence(
'make:htaccess',
'remove:config',
completed
);
} else {
// Full deploy
// Create array for additional tasks we can pipe things like bugsnag into (this can't be empty)
var extraTasks = ['remove:config'];
if (settings.env === settings.production) {
extraTasks.push('bugsnag'); // Add Bugsnag source maps on production
}
console.log('Installing composer packages..');
exec('composer install');
console.log('Installing NPM packages & pruning old packages..');
exec('npm prune');
// If deploying to a version then we don't want any potential package or package.lock changes saved
if (args.v) {
exec('npm install --no-save');
} else {
exec('npm install');
}
runSequence(
'make:htaccess',
'sass:compile',
'js:bundle-login',
jsBundle,
'copy-public',
extraTasks,
completed
);
}
if (args.u) {
console.log('Running unit tests..');
try {
exec('./vendor/bin/phpunit --bootstrap tests/unit/bootstrap.php -c tests/unit/phpunit.xml tests/unit');
} catch (e) {}
}
if (args.y) {
try {
console.log('Updating system packages..');
exec('[ -n "$(which yum)" ]');
exec('sudo yum -y update');
} catch (e) {
console.log('yum not found.');
}
}
}
};
composer.json:
{
"repositories": [
{
"type": "composer",
"url": "https://wpackagist.org"
},
{
"type": "git",
"url": "https://company/repo/iputils.git"
},
{
"type": "git",
"url": "https://company/repo/phpwhois.git"
}
],
"autoload": {
"psr-4": {"company\\Database\\": "database/src"}
},
"require": {
"php": ">=7.1",
"ext-dom": "*",
"ext-mbstring": "*",
"ext-pdo": "*",
"ext-SimpleXML": "*",
"adobe-marketing-cloud/marketing-cloud-php-sdk": "2.1.x",
"atrapalo/majesticseo-php-api-connector": "0.9.*",
"aveiv/open-exchange-rates-api": "1.1",
"aws/aws-sdk-php": "3.*",
"bshaffer/oauth2-server-php": "1.10",
"bugsnag/bugsnag": "^3.0",
"diggin/diggin-http-charset": "dev-master",
"eloquent/enumeration": "5.*",
"google/apiclient": "2.1.*",
"guzzlehttp/guzzle": "6.*",
"h4cc/wkhtmltopdf-amd64": "0.12.x",
"h4cc/wkhtmltoimage-amd64": "0.12.x",
"intervention/image": "^2.3",
"knplabs/knp-snappy": "^0.4.3",
"kunststube/rison": "0.92",
"league/csv": "^9.0",
"pelago/emogrifier": "#dev",
"php-di/php-di": "6.0.x",
"companyrepo/iputils": "dev-master",
"companyrepo/phpwhois": "dev-4-stable",
"ramsey/uuid": "2.8.*",
"shazam/php-slack": "^0.1.0",
"sameer-shelavale/php-countries-array": "*",
"symfony/intl": "^3.1",
"zendframework/zendframework1": "1.*",
"zendframework/zendframework": "3.*",
"zendframework/zend-http": "2.7.0",
"johnpbloch/wordpress-core-installer": "^1.0",
"johnpbloch/wordpress-core": "4.9.*",
"wpackagist-plugin/advanced-text-widget": "2.0.*",
"wpackagist-plugin/drafts-of-post-revisions": "0.8.*",
"wpackagist-plugin/image-widget": "4.2.*",
"wpackagist-plugin/inline-google-spreadsheet-viewer": "0.10.*",
"wpackagist-plugin/posts-to-posts": "1.6.*",
"wpackagist-plugin/post-types-order": "1.8.*",
"wpackagist-plugin/simple-page-ordering": "2.2.*",
"wpackagist-plugin/wp-migrate-db": "0.*",
"wpackagist-plugin/wp-cerber": "6.*",
"zircote/swagger-php": "dev-master",
"simshaun/recurr": "3.0.5",
"robmorgan/phinx": "*",
"fzaninotto/faker": "*"
},
"require-dev": {
"mockery/mockery": "^0.9.4",
"phpunit/phpunit": "6.*",
"phploc/phploc": "*",
"phpmd/phpmd": "*",
"slevomat/coding-standard": "~4.0",
"squizlabs/php_codesniffer": "3.*"
},
"extra": {
"wordpress-install-dir": "public/support/wp",
"installer-paths": {
"public/support/support-content/plugins/{$name}/": ["type:wordpress-plugin"]
}
}
}
Deploy command we run on production servers: gulp deploy -v tagversionnumber
Composer diagnose example from one of the prod servers:
Checking composer.json: WARNING
No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.
require.aveiv/open-exchange-rates-api : exact version constraints (1.1) should be avoided if the package follows semantic versioning
require.bshaffer/oauth2-server-php : exact version constraints (1.10) should be avoided if the package follows semantic versioning
require.diggin/diggin-http-charset : unbound version constraints (dev-master) should be avoided
require.pelago/emogrifier : unbound version constraints (#dev) should be avoided
require.companyrepo/iputils : unbound version constraints (dev-master) should be avoided
require.sameer-shelavale/php-countries-array : unbound version constraints (*) should be avoided
require.zendframework/zend-http : exact version constraints (2.7.0) should be avoided if the package follows semantic versioning
require.zircote/swagger-php : unbound version constraints (dev-master) should be avoided
require.simshaun/recurr : exact version constraints (3.0.5) should be avoided if the package follows semantic versioning
require.robmorgan/phinx : unbound version constraints (*) should be avoided
require.fzaninotto/faker : unbound version constraints (*) should be avoided
Checking platform settings: OK
Checking git settings: OK
Checking http connectivity to packagist: OK
Checking https connectivity to packagist: OK
Checking github.com rate limit: OK
Checking disk free space: OK
Checking pubkeys:
Tags Public Key Fingerprint: 57815BA2 7E54DC31 7ECC7CC5 573090D0 87719BA6 8F3BB723 4E5D42D0 84A14642
Dev Public Key Fingerprint: 4AC45767 E5EC2265 2F0C1167 CBBB8A2B 0C708369 153E328C AD90147D AFE50952
OK
Checking composer version: WARNING
You are not running the latest stable version, run `composer self-update` to update (1.3.0 => 1.7.2)
Some servers are running composer 1.2.2
On the same prod server composer install --dry-run:
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for zendframework/zend-soap 2.7.0 -> satisfiable by zendframework/zend-soap[2.7.0].
- zendframework/zend-soap 2.7.0 requires ext-soap * -> the requested PHP extension soap is missing from your system.
Problem 2
- zendframework/zendframework 3.0.0 requires zendframework/zend-soap ^2.6 -> satisfiable by zendframework/zend-soap[2.7.0].
- zendframework/zendframework 3.0.0 requires zendframework/zend-soap ^2.6 -> satisfiable by zendframework/zend-soap[2.7.0].
- zendframework/zend-soap 2.7.0 requires ext-soap * -> the requested PHP extension soap is missing from your system.
- Installation request for zendframework/zendframework 3.0.0 -> satisfiable by zendframework/zendframework[3.0.0].
To enable extensions, verify that they are enabled in your .ini files:
- /etc/php.ini
- /etc/php-7.1.d/10-opcache.ini
- /etc/php-7.1.d/20-bz2.ini
- /etc/php-7.1.d/20-calendar.ini
- /etc/php-7.1.d/20-ctype.ini
- /etc/php-7.1.d/20-curl.ini
- /etc/php-7.1.d/20-dom.ini
- /etc/php-7.1.d/20-exif.ini
- /etc/php-7.1.d/20-fileinfo.ini
- /etc/php-7.1.d/20-ftp.ini
- /etc/php-7.1.d/20-gd.ini
- /etc/php-7.1.d/20-gettext.ini
- /etc/php-7.1.d/20-iconv.ini
- /etc/php-7.1.d/20-imap.ini
- /etc/php-7.1.d/20-json.ini
- /etc/php-7.1.d/20-mbstring.ini
- /etc/php-7.1.d/20-mysqlnd.ini
- /etc/php-7.1.d/20-pdo.ini
- /etc/php-7.1.d/20-phar.ini
- /etc/php-7.1.d/20-posix.ini
- /etc/php-7.1.d/20-shmop.ini
- /etc/php-7.1.d/20-simplexml.ini
- /etc/php-7.1.d/20-sockets.ini
- /etc/php-7.1.d/20-sqlite3.ini
- /etc/php-7.1.d/20-sysvmsg.ini
- /etc/php-7.1.d/20-sysvsem.ini
- /etc/php-7.1.d/20-sysvshm.ini
- /etc/php-7.1.d/20-tokenizer.ini
- /etc/php-7.1.d/20-xml.ini
- /etc/php-7.1.d/20-xmlwriter.ini
- /etc/php-7.1.d/20-xsl.ini
- /etc/php-7.1.d/20-zip.ini
- /etc/php-7.1.d/30-mysqli.ini
- /etc/php-7.1.d/30-pdo_mysql.ini
- /etc/php-7.1.d/30-pdo_sqlite.ini
- /etc/php-7.1.d/30-wddx.ini
- /etc/php-7.1.d/30-xmlreader.ini
- /etc/php-7.1.d/40-apcu.ini
- /etc/php-7.1.d/php.ini
Note ext-soap is not on our local environments either, but install works fine there. And composer update works fine on both prod and local

You should install and enable php-soap extension.
zendframework/zend-soap 2.7.0 requires ext-soap * -> the requested PHP extension soap is missing from your system.

Related

Issue deploying to AppEngine (Flex) with specific PHP version

Since yesterday I can't deploy new versions of my PHP 5.6.* app to Google Cloud App Engine, by default is setting PHP 7.2.*
In the composer.json I do require the the correct version, this is the message
Step #0: There is no PHP runtime version specified in composer.json, or
Step #0: we don't support the version you specified. Google App Engine
Step #0: uses the latest 7.2.x version.
composer.json
{
"require": {
"php": "5.6.*",
"ext-mcrypt": "*",
"ext-imagick": "*",
"ext-mysql": "*",
"ext-zip": "*",
"ext-gd": "*",
"ext-mbstring": "*",
"ext-soap": "*",
"ext-bcmath": "*",
"ext-zip": "*",
"ext-curl": "*",
"ext-pdo_mysql": "*"
}
}
In the documentation clearly says it should be available
https://cloud.google.com/appengine/docs/flexible/php/runtime?hl=en
yaml file
runtime: php
api_version: 1
service: app-ecom-worker
env: flex
skip_files:
- ^(.*/)?#.*#$
- ^(.*/)?.*~$
- ^(.*/)?.*\.py[co]$
- ^(.*/)?.*/RCS/.*$
- ^(.*/)?\..*$
- ^(.*/)?Plugin(.*/)?webroot/
- ^(.*/)?queue.yaml
- ^(.*/)?ZohoReports/UploadTool/jre/lib/rt.jar
env_variables:
PARAM1: "production"
PARAM2: "10.72.0.3"
PARAM3: ebroot
PARAM4: ""
PARAM5: ebdb
PARAM6: 10.0.0.3
PARAM7: worker
CPWATCH: 0
MTNS_RPC: "x.x.x.x:8082"
MTNS_IO: "https://app.xxxx.com:843"
REDIS_LOG: 1
REDIS_LOG_DB: 2
REDIS_LOG_HOST: 10.0.0.3
REDIS_LOG_LIMIT: 50000
beta_settings:
cloud_sql_instances: fourth-carport-210916:us-east1:ecomexperts
runtime_config:
document_root: app/webroot
resources:
cpu: 2
memory_gb: 2
automatic_scaling:
min_num_instances: 1
max_num_instances: 4
cpu_utilization:
target_utilization: 0.95
Any Idea how to solve this?
You need to fix
"php": "7.2.*",
I deployed with Runtime PHP version 5.6 in App Engine Flexible and verified that the deployed version is 7.2 instead of 5.6. Alsos in the Step 0 when deploying, I saw that it was creating a Dockerfile with php72 image in place of php56 image.
It seems a bug so I created a Public Issue Tracker. You can see all the updates their related to PHP 5.6 version issue.

Facing issues on updating magento in magento cloud, updating magento to latest version of magento 2.3.2

Right now we are working on updating magento to latest version of magento 2.3.2
right now we are runing 2.2.7.
I following the guide for 2.3 branch found at
https://devdocs.magento.com/guides/v2.3/cloud/project/project-upgrade.html
I have taken following steps :
Step1: Update ece-tools version
On local workstation, perform an update using Composer
composer update magento/ece-tools
Add, commit, and push code changes.
git add -A && git commit -m “Update magento/ece-tools” && git push origin
Step2: Back up the database
Create a local backup of the remote database.
magento-cloud db:dump
when i run this command in my terminal i get
‘magento-cloud’ is not recognized as an internal or external command,
operable program or batch file.
Back up code and media.
php bin/magento setup:backup –code [–media]
To back up Staging or Production environment database before deploying
php vendor/bin/ece-tools db-dump
Step3: Complete the upgrade
I have PHP 7.1.30 version
Before completing the upgrade, update the autoload property
I follow all the steps giving in
https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#update-autoload
set the upgrade version using
composer require magento/product-community-edition 2.3.2 –no-update
Then Update the project
composer update
After composer update i get some error
Your requirements could not be resolved to an installable set of packages.
Problem 1
- magento/magento-cloud-metapackage 2.2.7 requires magento/product-enterprise-edition 2.2.7 -> satisfiable by magento/product-enterprise-edition[2.2.7] but these conflict with your requirements or minimum-stability.
- magento/magento-cloud-metapackage 2.2.7 requires magento/product-enterprise-edition 2.2.7 -> satisfiable by magento/product-enterprise-edition[2.2.7] but these conflict with your requirements or minimum-stability.
- Installation request for magento/magento-cloud-metapackage >=2.2.7 <2.2.8 -> satisfiable by magento/magento-cloud-metapackage[2.2.7].
can you please guide me how can i solve this issue..
Thanks.
My composer.json like as
{
"name": "magento/project-enterprise-edition",
"description": "eCommerce Platform for Growth (Enterprise Edition)",
"type": "project",
"version": "2.3.2",
"license": [
"OSL-3.0",
"AFL-3.0"
],
"repositories": {
"repo": {
"type": "composer",
"url": "https://repo.magento.com"
},
"amasty": {
"type": "composer",
"url": "https://composer.amasty.com/enterprise/"
}
},
"require": {
"magento/magento-cloud-metapackage": ">=2.2.7 <2.2.8",
"gene/bluefoot": "^1.0",
"amasty/promo": "^2.2",
"sashas/bug-from-email": "^2.0",
"amasty/shopby": "^2.11",
"amasty/label": "^1.10",
"connectpos/rest-api": "^1.1",
"magento/product-community-edition": "2.3.2",
"magento/product-enterprise-edition": "2.3.2"
},
"config": {
"use-include-path": true
},
"autoload": {
"psr-4": {
"Magento\\Framework\\": "lib/internal/Magento/Framework/",
"Magento\\Setup\\": "setup/src/Magento/Setup/",
"Magento\\": "app/code/Magento/",
"Zend\\Mvc\\Controller\\": "setup/src/Zend/Mvc/Controller/"
},
"psr-0": {
"": [
"app/code/",
"generated/code/"
]
},
"files": [
"app/etc/NonComposerComponentRegistration.php"
],
"exclude-from-classmap": [
"**/dev/**",
"**/update/**",
"**/Test/**"
]
},
"autoload-dev": {
"psr-4": {
"Magento\\Sniffs\\": "dev/tests/static/framework/Magento/Sniffs/",
"Magento\\Tools\\": "dev/tools/Magento/Tools/",
"Magento\\Tools\\Sanity\\": "dev/build/publication/sanity/Magento/Tools/Sanity/",
"Magento\\TestFramework\\Inspection\\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",
"Magento\\TestFramework\\Utility\\": "dev/tests/static/framework/Magento/TestFramework/Utility/"
}
},
"minimum-stability": "alpha",
"prefer-stable": true,
"extra": {
"magento-force": true,
"magento-deploystrategy": "copy"
},
"require-dev": {
"allure-framework/allure-phpunit": "~1.2.0",
"friendsofphp/php-cs-fixer": "~2.13.0",
"lusitanian/oauth": "~0.8.10",
"magento/magento-coding-standard": "~1.0.0",
"magento/magento2-functional-testing-framework": "~2.3.14",
"pdepend/pdepend": "2.5.2",
"phpunit/phpunit": "~6.5.0",
"sebastian/phpcpd": "~3.0.0",
"squizlabs/php_codesniffer": "3.3.1"
}}
error command line screenshot
you need to remove
"magento/product-community-edition": "2.3.2",
"magento/product-enterprise-edition": "2.3.2"
from composer.json, will be installed as dependencies of magento-cloud-metapackage
and change metapackage version
Try to switch php to php 7.2 or greater . Because from magento 2.3.2 , it requires php version >= 7.2
I think you need to update magento/magento-cloud-metapackage as well with a compatible version of Magento 2.3.2.
I found one article https://technicallysound.in/magento-2-upgrade-and-composer-issues/ that tried to solve similar issues during the Magento upgrade. But it is for the Community edition. Anyway composer issues are similar. In case the article could help you check for an updated version of the magento/magento-cloud-metapackage.
Your composer.json should be the same as magento/magento-cloud/composer.json

Adding league s3 filesystem breaks auto loading

After adding the Leauge S3 filesystem adaptor I receive the following auto loading error on my EBS system.
composer.json
"require": {
"php": ">=5.5.0",
"slim/slim": "2.3.2",
"slim/extras": "dev-develop",
"twig/twig": "1.*",
"directus/migrations": "dev-master",
"directus/permissions": "0.9.*#dev",
"directus/database": "~0.1.3",
"league/flysystem": "^1.0",
"league/flysystem-aws-s3-v3": "^1.0",
"swiftmailer/swiftmailer": "^5.4" },
Error:
Failed opening required
'/var/app/current/vendor/composer/../guzzlehttp/psr7/src/functions_include.php'
(include_path='/var/app/current/vendor/phpunit/php-token-stream:/var/app/current/vendor/phpunit/phpunit-mock-objects:/var/app/current/vendor/phpunit/php-code-coverage:/var/app/current/vendor/phpunit/phpunit:/var/app/current/vendor/symfony/yaml:.:/usr/share/pear7:/usr/share/php7')
in /var/app/current/vendor/composer/autoload_real.php on line 70
try updating composer with
>composer self-update
You can also clear the cache of composer launching the command:
>composer clear-cache
Hope this help

How to use the develop branch of Zend Framework 2 over composer?

In an Apigility driven application my composer.json is looking like this:
{
"name": "misc - myproject-api",
"description": "Skeleton Application for Apigility",
"require": {
"php": ">=5.3.23",
"zendframework/zendframework": ">=2.3.2,<3.0.0",
"zfcampus/zf-apigility": "~1.0",
"zfcampus/zf-apigility-documentation": "~1.0",
"zfcampus/zf-development-mode": "~2.0",
"zfcampus/zf-rest": "~1.0-dev",
"zf-commons/zfc-base": "dev-master",
"zendframework/zend-developer-tools": "dev-master",
"doctrine/doctrine-orm-module": "0.8.*"
},
"require-dev": {
"zendframework/zftool": "dev-master",
"zfcampus/zf-apigility-admin": "~1.0",
"zfcampus/zf-apigility-welcome": "~1.0",
"zfcampus/zf-deploy": "~1.0",
"zfr/zfr-cors": "~1.0",
"zend/zend-studio-development-mode": "~1.0"
},
"keywords": [
"api",
"apigility",
"framework",
"zf2"
],
"support": {
"email": "apigility-users#zend.com",
"irc": "irc://irc.freenode.net/apigility",
"source": "https://github.com/zfcampus/zf-apigility-skeleton",
"issues": "https://github.com/zfcampus/zf-apigility-skeleton/issues"
},
"extra": {
"branch-alias": {
"dev-master": "1.0-dev",
"dev-develop": "1.1-dev"
}
},
"config": {
"process-timeout": 5000
},
"type": "library",
"license": "BSD-3-Clause",
"homepage": "http://apigility.org/"
}
There is a ZF2 issue (that causes following error: Fatal error: Cannot use object of type Zend\Db\ResultSet\ResultSet as array). It has been fixed, but not merged to the master branch yet.
Since I need it working now, I tried to switch to the develop branch -- updated my composer.json
{
"name": "misc - myproject-api",
"description": "Skeleton Application for Apigility",
"require": {
"php": ">=5.3.23",
"zendframework/zendframework": "dev-develop as dev-master"
...
}
...
}
and executed a composer update:
$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
- Updating zendframework/zendframework (dev-master de98f63 => dev-develop be0b349)
Checking out be0b3496b73a61a255d05e945b75f6fdf0995c31
Writing lock file
Generating autoload files
Problem: I'm not observing any changes, the code seems still to be loaded from the ZF2 master branch (e.g. my local Zend\Paginator\Adapter\DbSelect has exactly the state of the according class in the master branch).
How to load the ZF2 develop branch?
UPDATE
I've triedthe the composer require direction value for the develop branch (2.4.*#dev) from the Packagist page of the Zend Framework. The result is the same as with dev-develop or dev-develop as dev-master -- the console shows the correct branch (or better the correct commit be0b349) downloading
$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
- Removing zendframework/zendframework (2.3.4)
- Installing zendframework/zendframework (dev-develop be0b349)
Cloning be0b3496b73a61a255d05e945b75f6fdf0995c31
Writing lock file
Generating autoload files
but after the updating, the code is still like in the master branch.
UPDATE
$ cd [project root directory]/vendor/zendframework/zendframework
$ git status
# On branch develop
nothing to commit (working directory clean)
That means, the branch is correct. And its also up-to-date, since the last commit , git log shows is be0b3496b73a61a255d05e945b75f6fdf0995c31 from 3d of February -- and that is actually the current HEAD revision.
So, the branch is correct, the revision is correct... Why is the code uot-of-date?
The "develop" branch has an alias to be version 2.4. You could require "2.4.*#dev" to get it.
If this breaks some of your dependencies, you could alias this with a 2.3 version.
"zendframework/zendframework": "dev-develop as 2.3.4.1"

Composer Use Github Before Packagist

I have made a fork of FOSRestBundle here RLovelett/FOSRestBundle it has a branch dev-411. I want to use my fork and branch of FOSRestBundle in a Symfony2 project.
To attempt this I patched my symfony2 project composer.json like so (full composer.json):
diff --git a/composer.json b/composer.json
index ec36007..19e82b5 100644
--- a/composer.json
+++ b/composer.json
## -23,7 +23,7 ##
"jms/security-extra-bundle": "1.4.*",
"jms/di-extra-bundle": "1.3.*",
"jms/serializer-bundle": "0.12.x-dev",
- "friendsofsymfony/rest-bundle": "0.11.*"
+ "friendsofsymfony/rest-bundle": "dev-411"
},
"scripts": {
"post-install-cmd": [
## -42,12 +42,18 ##
"config": {
"bin-dir": "bin"
},
- "minimum-stability": "alpha",
+ "minimum-stability": "dev",
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web",
"branch-alias": {
"dev-master": "2.2-dev"
}
- }
+ },
+ "repositories": [
+ {
+ "type": "vcs",
+ "url": "https://github.com/RLovelett/FOSRestBundle"
+ }
+ ]
}
When I run composer update I get the following error message:
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package friendsofsymfony/rest-bundle dev-411 could not be found.
Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.
Read <http://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.
What is wrong with my configuration?
Composer prefixes dev- to branch names to identify them clearly, so if the branch is dev-411, the composer version for it would be dev-dev-411.
Try this : "friendsofsymfony/rest-bundle": "0.11.dev-feature/411"
More infos here : https://github.com/composer/composer/issues/935

Categories