Skip to content
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 installation fail #25

Closed
egeloen opened this issue Mar 27, 2012 · 4 comments
Closed

Composer installation fail #25

egeloen opened this issue Mar 27, 2012 · 4 comments

Comments

@egeloen
Copy link

egeloen commented Mar 27, 2012

Hey,

We can't install the bundle using composer. Composer tries to find the commit 63c990abc320828376671a0bd0ed861db6b9ad69 that does not exist on master.

@stof
Copy link
Member

stof commented Mar 27, 2012

I forced the update on packagist so it should be fixed now

@stof stof closed this as completed Mar 27, 2012
@willdurand
Copy link
Member

Yes it works. I forced the update too, but it was without effect... Maybe the last PR fixed the reference commit (I've configured the Packagist GH hook).

@willdurand
Copy link
Member

When I say, "I forced the update", it was on packagist.org, not from the hook (even if I tried too).

@stof
Copy link
Member

stof commented Mar 27, 2012

@willdurand yeah, the point is that the github API was still giving the old commit even when forcing packagist to recrawl (as the force push did not seem to trigger it). It is fixed now because I merged another PR and so added new commits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants