Ignore $out/bin/*.lock files during buildPhase makeWrapper #53
Conversation
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
Since Ruby 3.3.5, the bin/ dir contains a non-executable *.lock file per executable -- unclear if this is intentional, but it means `makeWrapper` fails the build when those files are encountered.
|
Running a tight schedule lately, sorry for the delay. I will try replicating this on 3.3.5 |
|
This is happening for me as well and I've avoided upgrading to 3.3.5 till things can get ironed out. |
|
Looks like this was a problem with rubygems that has been corrected but will not land until Ruby v3.3.6. This PR could work around the issue, but I wonder if we could also bring in a more recent version of rubygems and/or bundler to help out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Since Ruby 3.3.5, the bin/ dir contains a non-executable *.lock file per executable -- unclear if this is intentional, but it means
makeWrapperfails the build when those files are encountered.