-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Installing zf2 on travis via composer got output backplane/zendframework ? #5832
Comments
backplane/zendframework showed when installing zf2.2.* and doctrine-(orm-)module 0.9.* because doctrine module bumped zf2 to 2.3.* and backplane/zendframework registered itself as alternative to zf2 - so composer instead of saying "2.2.5 not 2.3.* STOP" found alternative dev-develop. There is composer/composer#2690 about composer doing it automatically without warning but in cases I met, it was packages incompatibility and composer "too succesful" in resolving dependencies. backplane/zendframework was removed after someone from IRC mailed them few days ago. |
the solution ? |
backplane/zendframework was removed from both github and packagist within hours of people complaining about this. I'm not sure how composers cache works. But the day after I still got backplane when trying to update my project. Tried to "debug" it by installing one dependency at a time but never ran into the problem again. So I guess it was some kind of cache that got removed when I removed all dependencies in my composer.json and did an update. |
@grizzm0 I tried locally and work, but at travis-ci.org seems it still load from backplane/zendframework :( |
The simplest way to fix this temporarily is to add |
It was fixed in Composer? Seems a security issue to me. |
@samsonasik i had the same issue. Seems to be solved now. About the security issue @padraic blogged something |
yes, closing ;), Thanks all ;) |
I see at the develop branch, on travis, it got error when installing zendframework/zendframework :
I tried at my local PC to install zendframework/zendframework via composer and got same output :
![installing-zf2-backplane](https://camo.githubusercontent.com/f3a164627bf7f3cd41589243aad650f05c38d214b929290a5d0cafd463c5498a/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f3435393634382f323138303339352f38303364393239612d393731362d313165332d386338322d3964643736393863643664382e706e67)
Any something happen on composer or any addition setting required ?
The text was updated successfully, but these errors were encountered: