Have travis CI use older version of composer to avoid case issues with pear package. #1083
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This didn't turn out well, it is now giving an error PEAR packages were removed from composer 2.0 - so evidently the fix requires further tinkering with the dependencies of composer and limiting the version travis uses. |
|
So the fix here evidently is to have travis use composer 1.8 vs. the latest one. It no longer complains about case and doesn't break the integration tests. |
Robbt
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that the CI tests were failing due to a simple warning elevated to error about casing of the pear packages. So this is my attempt to resolve that issue.