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_buildfarm scripts locally.
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.