New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composer cannot resolve dependencies (SolverProblemsException) #27
Comments
@JeroenDeDauw Maybe because |
Ah, yeah, this was me. Shame on me. Still will be nice to run master somehow ... Just got the next "complaint" but this time with SQC. @JeroenDeDauw Could you stretch out a bit and provide fluff ... |
This proves my hypothesis for those that don't have yet a "real" release. |
SQC is Semantic Compound Queries which does have a real release. There must be something else in the water. |
Composer seems to be picking a random problem instead of just printing all of them. Now it is the Semantic Meta Tag extension causing pain. |
For:
I'm not sure why |
Sure and it is getting even better. This one all of a sudden looks for ~2.1:
I have to leave for about two hours now. |
I suspect that since now SMW master is on |
Though the constraint should probably be |
|
Ah, I am with you and Composer. |
I have done the changes for some extensions. If these get through ok I could do the rest too. |
Paradise regained:
|
Well, for now (since there is no 3.0 release only a |
I'm also skeptical of this change. Now when you make a breaking change in SMW, extensions might break, and you need to make matching changes right away. Of course this only happens for those that pull in @dev stuff (and thus SMW 3.0-dev) or once SMW 3.0 is actually released. I suppose this can be dealth with, if you have control over the affected extensions and are willing to update them in step with SMW. That might still take more time though, and be problematic in cases where you can't switch to a new construct because you still need to support the old one or lose compat with all non-dev-SMW. Even then it seems poor form to specify this compat for non-dev. I suspect you can have something like |
@JeroenDeDauw @mwjames We have to rethink how the dependencies are set up. What currently happens is that Composer installs |
Hi,
***@***.***"` so we currently have "Semantic MediaWiki 2.5.0 (ec6d5c1) 15:13, 26
March 2017" installed on sandbox even though we have done all these changes
referenced above and use this
I removed the 3.0 reference in SemanticGlossary for the expected
release therefore I believe it selects the best matchable release
which is 2.5. I'm guessing but after the release, when you re-add the
~3.0 as constraint, the sandbox will pull in the master again.
Cheers
…On 3/27/17, Karsten Hoffmeyer ***@***.***> wrote:
@JeroenDeDauw @mwjames We have to rethink how we set up the dependencies.
What currently happens is that Composer installs ***@***.***"` instead of
***@***.***"` so we currently have "Semantic MediaWiki 2.5.0 (ec6d5c1) 15:13, 26
March 2017" installed on sandbox even though we have done all these changes
referenced above and use this
[composer.local.json](https://sandbox.semantic-mediawiki.org/wiki/SMW_Sandbox:Setup_information#composer.local.json)
file. So somewhere still a dependency is required that disallows going dev
master. I am sure there is a way but currently we are only guessing how this
way may look like.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#27 (comment)
|
Ah, I see. I guess I'm up now. :) Thanks for the info! |
Affirmative - we are in fluff again. |
One of todays changes causes Composer failures when running master
@mwjames Do you have an idea which one may have caused this and provide fluff ... Since Semantic Notification was not touched ...?
The text was updated successfully, but these errors were encountered: