your requirements could not be resolved to an installable set of packages что делать
Error:Your requirements could not be resolved to an installable set of packages.(on server)
I am using laravel 5.3 for my project.Now I am setting it up to the server.
The problem occured when doing so.And i am stuck at this point of error.
command following error occurs:
6 Answers 6
Your PHP need some ext for run your packages.
You can install that with apt-get if you use Ubuntu and PHP 5 :
After that restart your web service then it will work.
First, check if composer is installed by doing.
If it is installed, do the following sequence. This worked for me:
Then finally do this.
When I went to create a laravel project, I got this problem.
After googling, I got this solution.
I followed these steps:
Step 2: sudo apt-get install php7.2-intl
Step 3: sudo apt-get install php7.2-xsl
Step 4: sudo apt-get install php7.2-mbstring
After following these steps just restart the server again.
And then create a new laravel project by typing: «composer create-project laravel/laravel projectname» in your terminal.
Your requirements could not be resolved to an installable set of packages. #6954
Comments
Turtlesfr commented Dec 29, 2017
I know this is a common issue but I can’t find a solution. When I deploy my Symfony app (which run good locally and Composer as well), I run into the
I have PHP7.1 both locally and on remote.
The only difference I can see is Composer version (I have the latest locally while on remote, it’s the v1.1.1). I can’t update this version because it’s on a managed VPS.
Here is my composer.json :
The text was updated successfully, but these errors were encountered:
tomzx commented Jan 5, 2018 •
Turtlesfr commented Jan 5, 2018
Thank you for your help
lsp-rs commented Jun 20, 2018
Olá tive esse problema Your requirements could not be resolved to an installable set of packages.
No meu caso isso foi porque o php-xml não estava instalado.
assisti um vídeo https://www.youtube.com/watch?v=1MZZ6o3bHNw
resumindo sudo apt install php-xml
Hello, I had this problem. Your requirements could not be resolved to an installable set of packages.
In my case this was because php-xml was not installed.
I watched a video https://www.youtube.com/watch?v=1MZZ6o3bHNw
summarizing sudo apt install php-xml
sgnota commented Jan 22, 2019
Olá tive esse problema Your requirements could not be resolved to an installable set of packages.
No meu caso isso foi porque o php-xml não estava instalado.
assisti um vídeo https://www.youtube.com/watch?v=1MZZ6o3bHNw
resumindo sudo apt install php-xml
Hello, I had this problem. Your requirements could not be resolved to an installable set of packages.
In my case this was because php-xml was not installed.
I watched a video https://www.youtube.com/watch?v=1MZZ6o3bHNw
summarizing sudo apt install php-xml
Same problem here and it was fixed the same way thanks
petertwise commented Dec 20, 2020
—ignore-platform-reqs helped me solve running composer install in a github actions automation successfully.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Your requirements could not be resolved to an installable set of packages #5898
Comments
alainib commented Nov 23, 2016 •
Hello, i get a 3 years old untouched project. I need to add gaufrette bundle in this project and tweak it.
the original composer.json :
this composer.json work if i don’t change anything. i can make composer install
Output of php composer.phar diagnose :
No license specified, it is recommended to do so. For closed-source software you may use «proprietary» as license. Defining autoload.psr-0 with an empty namespace prefix is a bad idea for performance require.symfony/icu : exact version constraints (1.1.x-dev) should be avoided if the package follows semantic versioning require.doctrine/mongodb-odm-bundle : unbound version constraints (dev-master) should be avoided require.white-october/pagerfanta-bundle : unbound version constraints (dev-master) should be avoided require.jms/translation-bundle : unbound version constraints (dev-master) should be avoided require.escapestudios/wsse-authentication-bundle : exact version constraints (2.3.x-dev) should be avoided if the package follows semantic versioning require.jms/i18n-routing-bundle : unbound version constraints (dev-master) should be avoided require.raulfraile/ladybug-bundle : unbound version constraints (dev-master) 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 Tags Public Key Fingerprint: 57815BA2 7E54DC31 7ECC7CC5 573090D0 87719BA6 8F3BB723 4E5D42D0 84A14642 Dev Public Key Fingerprint: 4AC45767 E5EC2265 2F0C1167 CBBB8A2B 0C708369 153E328C AD90147D AFE50952 Checking composer version: OK
I wanted to change all the dev-master to fixed version. So i get the composer.lock created 3 years ago and get the version of each bundle from «extra»: < "branch-alias": < "dev-master": "XXX" >>,
So my new composer.json ( a changed the A.B.x-dev syntax with A.B.* each times )
So i try to php composer.phar update but i get erros depending on wich dev-master bundle i change
I get the following output:
The text was updated successfully, but these errors were encountered:
Comments
IftakharBappy commented Aug 22, 2016
$ composer require barryvdh/laravel-dompdf
Using version ^0.7.0 for barryvdh/laravel-dompdf
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
The text was updated successfully, but these errors were encountered:
barryvdh commented Aug 23, 2016
laravel/dompdf 0.7 only supports dompdf 0.7. Try removing dompdf/dompdf from you composer file.
mvpasarel commented Aug 24, 2016
I was using «yajra/laravel-datatables-oracle»: «^6.11» which depends on «dompdf/dompdf»: «^0.6.1» so I used composer aliases to fix it:
barryvdh commented Aug 24, 2016
Ah, I guess it would be best if the package from @yajra would also be updated.
mvpasarel commented Aug 24, 2016
Exactly. But for now this made it work.
mvpasarel commented Aug 24, 2016
Seems like its updated and I maybe using an older version of datatables yajra/laravel-datatables#496.
larsbo commented Sep 2, 2016
had the same error.
The solution for me was as simple as:
composer remove barryvdh/laravel-dompdf
composer require barryvdh/laravel-dompdf
VickG commented Nov 3, 2016
I tried what you suggested, but I am still getting:
kangyasin commented Apr 4, 2018
hello you can try with
work tested in laravel version 5.6 maybe same in 5.4
lois-dowell commented Aug 11, 2018 •
hello
i have issues like
ErrorException in Block.php line 714:
A non-numeric value encountered
Exception in Inline.php line 48:
No block-level parent found. Not good.
stale bot commented Jul 29, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Any issues with PDF rendering itself that are not directly related to this package, should be reported on https://github.com/dompdf/dompdf instead. When having doubts, please try to reproduce the issue with just dompdf.
If you believe this is an actual issue with the latest version of laravel-dompdf, please reply to this issue so we can investigate further.
Thank you for your contribution! Apologies for any delayed response on our side.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Your requirements could not be resolved to an installable set of packages что делать
rpsimao\/invoicexpress-api 0.5.6 requires laravel\/framework 5.4.* \n
It doesn’t appear to be actively maintained. The ast commit mentions supporting auto-discovery (5.5) but the composer.json file is locked to illuminate\/framework and illuminate\/support versions 5.4.* \n
You could (i) submit a PR with the required update to the original package, (ii) fork the repo and require your changed version in your project or (iii) find a different package that does what you need. \n»,»bodyInMarkdown»:»It doesn’t appear to be actively maintained. The ast commit mentions supporting auto-discovery (5.5) but the composer.json file is locked to illuminate\/framework and illuminate\/support versions 5.4.*\r\n\r\nYou could (i) submit a PR with the required update to the original package, (ii) fork the repo and require your changed version in your project or (iii) find a different package that does what you need.»,»replies»:[],»user»:<"id":6962,"username":"tykus","avatar":"\/\/unavatar.now.sh\/github\/tykus","experience":<"award_count":"2,541","level":50,"points":"1,665,200","pointsUntilNextLevel":"0">,»achievements»:[],»reported»:null,»staff»:false,»profile»:<"full_name":null,"bio":null,"twitter":"","github":"tykus","website":"","employment":"Tykus Web Development","job_title":"Full Stack PHP Developer","location":"Dublin","flag":"ie","available_for_hire":1>,»dateSegments»:<"created_diff":"7 years ago">,»settings»:<"show_profile":true>,»links»:<"profile":"https:\/\/laracasts.com\/@tykus">>,»likes»:[«johnk»],»created_at»:»2018-06-15T07:20:58.000000Z»,»links»:<"delete":"\/discuss\/replies\/433352","like":"\/discuss\/replies\/433352\/likes","best_answer":"\/discuss\/conversations\/88332\/best">,»best_answer»:true,»dateSegments»:<"createdDiff":"3 years ago">>,<"id":433370,"conversation_id":88332,"body":"
You would fork the repo in Github, which will give you a version of the project in your Github account. \n
You can clone your version of the project locally. \n
git clone https:\/\/github.com\/your-github-username\/invoicexpress-api\n \n
. and make the change(s) required to get it working (might be only to change the composer.json to require more recent versions of Laravel. \n
Run composer update and run the test suite on the project to see if changes worked. \n
Finally, add the following to the composer.json file to require the repository in your project: \n
Yes, you would need to create a Github account. \n
Thanks, Im gettning this error «In ProviderRepository.php line 208: \n
Class ‘rpsimao\\InvoiceXpressAPI\\InvoiceXpressAPIServiceProvider’ not found».\n \n
With this command: \n