Virtual package support
See original GitHub issueI`m trying ti install “geocoder-php/common-http”: “4.0.0” through composer proxy.
I got an error:
Problem 1 - Installation request for geocoder-php/common-http 4.0.0 -> satisfiable by geocoder-php/common-http[4.0.0]. - geocoder-php/common-http 4.0.0 requires psr/http-message-implementation ^1.0 -> no matching package found.
After this error i`m trying to add “guzzlehttp/psr7” which implements Virutal package “psr/http-message-implementation” but error stays.
Everything works fine with original http://packagist.org
Can you please help to solve this issue or provide some fix for nexus composer?
Thank you.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:13 (3 by maintainers)
Top Results From Across the Web
What's a virtual package? - Ask Ubuntu
A virtual package is a generic name that applies to any one of a group of packages, all of which provide similar basic...
Read more >Debian GNU/Linux FAQ - 6.8 What is a Virtual Package?
A virtual package is a generic name that applies to any one of a group of packages, all of which provide similar basic...
Read more >What is a Virtual Package | UPack - Inedo's Documentation
A virtual package is just like a regular package, except without any actual content (i.e. your application files and components).
Read more >Contact Us | UPS - United States
Get answers to all your questions using our virtual assistant, live chatting a representative or calling the UPS support line best suited for...
Read more >7. Declaring relationships between packages - Debian
A virtual package is one which appears in the Provides control field of another ... than strictly earlier/later. dpkg still supports them with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I need to do more research but this seems to be some kind of composer bug actually. Nexus doesn’t strip “provide” metadata from packages it hosts, but for some reason composer completely ignores it.
EDIT: Well nvm, composer has it implemented very weird but the issue is on the Nexus side of things.
hey @theravel just add this under the autoload-dev to get sentry working.