fix: repair broken cp/mkdir lines in yumrepo Dockerfile - #17
Merged
Merged
Conversation
Leftovers from el7 removal broke the yumrepo build:
- `cp -pr releases/centos/{x86_64,aarch64}/2/` had no destination
operand. These lines used to copy the el7 libnss rpm into the
Amazon Linux 2 repo, but libnss no longer ships an el7 build.
- `mkdir -p releases/centos/{x86_64,aarch64}/{2}` created a literal
`{2}` directory since bash does not expand a single-element brace,
so the later `cp` into `.../2` failed with "target is not a directory".
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.
Leftovers from el7 removal broke the yumrepo build:
cp -pr releases/centos/{x86_64,aarch64}/2/had no destination operand. These lines used to copy the el7 libnss rpm into the Amazon Linux 2 repo, but libnss no longer ships an el7 build.mkdir -p releases/centos/{x86_64,aarch64}/{2}created a literal{2}directory since bash does not expand a single-element brace, so the latercpinto.../2failed with "target is not a directory".