[#28806] Re-install of a gem can leave prior gem files remaining (take 2)#29
Merged
3 commits merged intoFeb 16, 2011
Merged
Conversation
A case of this arises from 72d751e in combination with the HACK of test_gem_uninstaller:14, adding executables to the spec not found in the test gem. It should be harmless to only chmod existing files, and silently ignore missing executables in any case.
Member
|
Applied! |
4 tasks
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is rework of patch #18 where I've rebased to master and added the requested test case.
This patch addresses the issue described in tracker #28806 on rubyforge:
http://rubyforge.org/tracker/index.php?func=detail&aid=28806&group_id=126&atid=575
In summary, it assures that older same-version gem files are removed before a gem is installed.