I want to install assortment bundle in symfony 2.2.1.
I added
"sylius/assortment-bundle" : "*" in composer.json
and run
composer require sylius/assortment-bundle:*
but showig error:
The requested package sylius/assortment-bundle could not be found in any version, there may be a typo in the package name.
blem 2
Please try with sylius/assortment-bundle": "0.1.*#dev".
Related
I am trying to install the Reset Password Feature on my symfony application.
The Problem is that Composer tell me that :
Your requirements could not be resolved to an installable set of packages.
Problem 1
- php is present at version 8.1.0 and cannot be modified by Composer
- symfonycasts/reset-password-bundle v1.16.0 conflicts with php >=8.1 <8.1.10.
- Root composer.json requires symfonycasts/reset-password-bundle ^1.16 -> satisfiable
by symfonycasts/reset-password-bundle[v1.16.0-password-bundle[v1.16.0].
You can also try re-running composer require with an explicit version constraint,
e.g. "composer require symfonycasts/reset-password-buycasts/reset-password-bundle:*"
to figure out if any version is installable, or "composer require symfonycasts/e-paif
you know which yondle:*" to figure out if any version is installable, or
"composerreset-password-bundle:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
So, do I have to install a specific version ?
If you look at the composer.json of the Reset Password Bundle, you can see that there is a conflict with PHP version 8.1.0, 8.1.1, ... 8.1.10.
"conflict": {
"php": ">=8.1 <8.1.10",
"doctrine/orm": "<2.7"
},
So, yes, you have to upgrade your stack to PHP version 8.1.11
This pull request give explanations why this bundle is currently no more compatible with these PHP versions.
In a Symfony 4 project, I'm getting problems after a composer selfupdate to 2.1 (from 1.x). One of the error messages when hitting
composer update nothing
is:
Root composer.json requires ocramius/package-versions == 1.3.0.0 -> satisfiable by ocramius/package-versions[1.3.0].
What is really strange in my opinion is that my composer.json does not contain any references to "ocramius/package-versions" and somehow I don't manage to trace where it comes from. Even stranger: When I try
composer show ocramius/package-versions --tree
I get
[InvalidArgumentException]
Package ocramius/package-versions not found
The only references to "ocramius/package-versions" in my project come from
composer.lock
vendor/composer/package-versions-deprecated/composer.json
vendor/composer/installed.json
It seems it is stuck in the composer.lock, but I dont want to run a real composer update on the whole project because of side effects. Any ideas what I could do?
EDIT:
After getting poked into the direction of composer why I managed to find out why ocramius/package-versions is included at all, but still 1.3.0:
$ composer why ocramius/package-versions
composer/package-versions-deprecated 1.11.99.2 replaces ocramius/package-versions (1.11.99)
ocramius/package-versions 2.3.0 replaces composer/package-versions-deprecated (*)
$ composer why composer/package-versions-deprecated
composer/package-versions-deprecated 1.11.99.2 replaces ocramius/package-versions (1.11.99)
doctrine/migrations 3.2.0 requires composer/package-versions-deprecated (^1.8)
doctrine/orm 2.7.5 requires composer/package-versions-deprecated (^1.8)
symfony/proxy-manager-bridge v4.4.25 requires composer/package-versions-deprecated (^1.8)
Ok, so I finally found why the packages is included. But why the wrong version?
Then the scales fell from my eyes: Why not just update it instead of trying to find out why this version is chosen...???
A simple
composer update ocramius/package-versions
did the trick. D'oh!
As you can see on the packagist page of that package, v1.3.0 is not compatible with Composer v2, as it requires composer-plugin-api: ^1.0.0. You need to update that package if you want to use Composer v2.
If you want to check which package requires this one, you can use composer why
I have successfully setup a symfony 3.2.4 project with the following commands :
symfony new symfony_test
cd symfony_test
composer require --dev phpunit/phpunit ^6.0
composer update
Then I have the following error when I try to run the default test :
$ vendor/bin/phpunit tests/AppBundle/Controller/DefaultControllerTest.php
Fatal error: Class 'PHPUnit_Framework_TestCase' not found in C:\Users\po.louis\PhpstormProjects\test\symfony_test\vendor\symfony\symfony\src\Symfony\Bundle\FrameworkBundle\Test\KernelTestCase.php on line 23
What am I missing?
Seems not possibile yet on same version of the framework, as announced in the last weekly update:
This week Symfony continued refactoring tests to make use of the
new PHPUnit namespaces.
Hope this will be available on all the supported version.
Inside your composer.json edit
phpunit/phpunit ^6.0
to
phpunit/phpunit ^5.7
and all works fine.
As Matteo wrote to you isn't supported yet 6.0 version
https://github.com/artseld/ArtseldOpeninviterBundle
I cant install this bundle in my symfony 2.2.
Problem 1
- The requested package artseld/openinviter-bundle could not be found in any version, there may be a typo in the package name.
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.
Anybody knows what is a problem?
This bundle does not exist in packagist yet.
So you will have to use git submodules instead:
git submodule add http://github.com/artseld/ArtseldOpeninviterBundle.git vendor/artseld/OpeninviterBundle
Alternatively, it could be a good idea to ask the maintainer of the repo to support installation via composer and add the bundle to packagist. You could potentially request this feature by opening an issue in the repo directly.
I want to install the Buzz bundle. On GitHub, the installation instructions suggest the .bin/vendors install method. However, that's not supported in Symfony 2.2.0.
Is there another way I could install the bundle? I've been trying to install it using Composer, but without any luck.
Try adding in composer.json under require key:
"sensio/buzz-bundle": "dev-master"
Then follow the instructions from step3 onward
You'll also need to run composer.phar update after that.
And for future reference, lookup the package you need on packagist.org. You'll find there what you need to put in composer.json