Support unsigned apt repositories #947
Merged
Conversation
This file contains 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
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 a non-breaking change to support unsigned apt repositories. Because the configuration file format for repository information is structured as two separate lists for repository URLs and keys, an empty string for the key indicates that the repository should be used without checking signatures.
The empty file is still written out to a file so that downstream buildfarm scripts in the chain don't need to be updated and simply carry forward the empty file.
While this behavior isn't desirable in our production environments at all, it would lower the barrier for entry when running
ros_buildfarmscripts locally.This is already how the RPM repositories behave.