Update remote if url has changed

[evallesp]

Previously we were checking if the remote name is there to add it. Now, if the patches_repo url has changed, but we maintain the same remote_name, this is updated.

For doing this, we just check if the remote_name exists and if the patches_repo differs from its value. If so, we just remove the remote so next line below it'd recreate it.

Not it's based on new git_wrapper version that allows to return the remote dict with its value but also to remove the remote.

Requires: release-depot/git_wrapper#114

[jguiditta]

MInor wording suggestions, otherwise this seems fine to me. I do wonder if perhaps we should bump the version of git_wrapper dep though. Then we can do a 2.3 release over there to add the new method in your patch, and guarantee this will get the expected functionality.

[jguiditta]

MInor wording suggestions, otherwise this seems fine to me. I do wonder if perhaps we should bump the version of git_wrapper dep though. Then we can do a 2.3 release over there to add the new method in your patch, and guarantee this will get the expected functionality.

Any thought on making git_wrapper version dependency be 2.3 to guarantee the expected feature is there? Also, I think we should do that release before merging to, to avoid any issues.

[evallesp]

MInor wording suggestions, otherwise this seems fine to me. I do wonder if perhaps we should bump the version of git_wrapper dep though. Then we can do a 2.3 release over there to add the new method in your patch, and guarantee this will get the expected functionality.

Any thought on making git_wrapper version dependency be 2.3 to guarantee the expected feature is there? Also, I think we should do that release before merging to, to avoid any issues.

Done!

[jguiditta]

ACK, this looks good to me! I'll tag git_wrapper so it does a build as soon as that patch merges

[jguiditta]

Just realized - git_wrapper is already tagged up to0.2.10, so we should make this require 0.2.11

[evallesp]

recheck

[eggmaster]

LGTM!