Fix your broken Symfony2 with PRs available

Today I did bin/vendors update and got all messed up with AsseticBundle first.
I was told I needed to update my repos with some PRs that fixed the problem.

I had already blogged about handling PRs from other people into ones repo. However never had this scenario before.

So what I did was:

1
2
3
4
cd vendor/bundles/Symfony/Bundle/AsseticBundle
git remote add fix https://github.com/jstout24/AsseticBundle.git
git fetch fix
git cherry-pick 40bdc973dfaa5aabf51f

What I have done is:
1. went into the problematic repo directory
2. added a remote address of the repo where the PR originated
3. fetch the changes including the commit that has the fix
4. select in particular that commit and apply it to fix my local repo

I am going to fix other parts with other PRs, now wondering what do I do to tell bin/vendors update not to touch these changes.

If you are like me with SE (symfony-standard editon) do this after applying the two or more patches available:

cp deps deps.old
pico deps
//comment the lines of problematic repos
bin/vendors update
// this time clean update

After this operation when the PRs are merged to main repo, it is enough if you just change back the deps file and do bin/vendors update.

In addition to this another way of fixing problems is going backwards. Since with SE symfony-standard edition you have been using git versioning, then you just need to look for earlier commits with valid deps and then the only command needed after reverting back to a valid state would be to issue bin/vendors install.

Please consider donating. Thanks!

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">