Closed pliniocsfernandes closed 10 years ago
Hi :)
Could you try changing your composer.json to point to a testing branch that I just setup? It looks like I had to update the composer.lock file, but also it seems that the root project (your code, that is) needs to include log4php as a dependency, since it's not coming from packagist
If you confirm that everything works ok, I'll merge.
This is the composer.json that I tried:
{
"require": {
"marcelog/pami": "dev-marcelog_composer_test",
"pear-log4php/Apache_log4php": ">=2.1.0"
},
"repositories": [
{
"type": "pear",
"url": "http://pear.apache.org/log4php/"
}]
}
Thanks in advance :)
I tried the composer self-update
again:
Use composer self-update --rollback to return to version 7343198817f365b1676ced0f353808f0e408ff9a
And now the issue seems to be gone. Taking a look at the last composer commits I think that my problem was related to a failed HTTP request.
Sorry for the trouble and thanks for the help. :)
We are still seeing this issue. I am having to revert back to composer 1.0.0-alpha8 to get composer to install. Can we not use this repo in place of the pear repo: https://packagist.org/packages/apache/log4php
I used
sudo composer self-update
to update composer:Then I tried using
composer update
and got the following error:So I used
sudo composer self-update --rollback
to revert the composer version:And the
composer update
worked normally again.The setup I'm using on composer.json is the same described on the README: