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

Installing zf2 on travis via composer got output backplane/zendframework ? #5832

Closed
samsonasik opened this Issue Feb 16, 2014 · 8 comments

Comments

Projects
None yet
6 participants
@samsonasik
Contributor

samsonasik commented Feb 16, 2014

I see at the develop branch, on travis, it got error when installing zendframework/zendframework :

 - Installing backplane/zendframework (2.2.5)

Downloading: connection...

[Composer\Downloader\TransportException]

The "https://api.github.com/repos/Backplane/zf2/zipball/4a7cf6a4cf791244e14

aa0ca49d1f06916b63202" file could not be downloaded (HTTP/1.1 404 Not Found

) 

I tried at my local PC to install zendframework/zendframework via composer and got same output :
installing-zf2-backplane

Any something happen on composer or any addition setting required ?

@jkavalik

This comment has been minimized.

Show comment
Hide comment
@jkavalik

jkavalik Feb 16, 2014

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.

jkavalik commented Feb 16, 2014

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.

@samsonasik

This comment has been minimized.

Show comment
Hide comment
@samsonasik

samsonasik Feb 16, 2014

Contributor

the solution ?

Contributor

samsonasik commented Feb 16, 2014

the solution ?

@grizzm0

This comment has been minimized.

Show comment
Hide comment
@grizzm0

grizzm0 Feb 16, 2014

Contributor

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.

Contributor

grizzm0 commented Feb 16, 2014

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.

@samsonasik

This comment has been minimized.

Show comment
Hide comment
@samsonasik

samsonasik Feb 16, 2014

Contributor

@grizzm0 I tried locally and work, but at travis-ci.org seems it still load from backplane/zendframework :(

Contributor

samsonasik commented Feb 16, 2014

@grizzm0 I tried locally and work, but at travis-ci.org seems it still load from backplane/zendframework :(

@Ocramius

This comment has been minimized.

Show comment
Hide comment
@Ocramius

Ocramius Feb 16, 2014

Member

The simplest way to fix this temporarily is to add "conflict":{"backplane/zendframework":"*"} to your composer.json and then analyze why the set of requirements cannot be resolved.

Member

Ocramius commented Feb 16, 2014

The simplest way to fix this temporarily is to add "conflict":{"backplane/zendframework":"*"} to your composer.json and then analyze why the set of requirements cannot be resolved.

@danizord

This comment has been minimized.

Show comment
Hide comment
@danizord

danizord Feb 17, 2014

Contributor

It was fixed in Composer? Seems a security issue to me.

Contributor

danizord commented Feb 17, 2014

It was fixed in Composer? Seems a security issue to me.

@ThaDafinser

This comment has been minimized.

Show comment
Hide comment
@ThaDafinser

ThaDafinser Feb 25, 2014

Contributor

@samsonasik i had the same issue. Seems to be solved now.

About the security issue @padraic blogged something
http://blog.astrumfutura.com/2014/02/composer-downloading-random-code-is-not-a-security-vulnerability/

Contributor

ThaDafinser commented Feb 25, 2014

@samsonasik i had the same issue. Seems to be solved now.

About the security issue @padraic blogged something
http://blog.astrumfutura.com/2014/02/composer-downloading-random-code-is-not-a-security-vulnerability/

@samsonasik

This comment has been minimized.

Show comment
Hide comment
@samsonasik

samsonasik Feb 26, 2014

Contributor

yes, closing ;), Thanks all ;)

Contributor

samsonasik commented Feb 26, 2014

yes, closing ;), Thanks all ;)

@samsonasik samsonasik closed this Feb 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment