4f0342be70
Sharing an updates file between the Debian and Ubuntu reprepro runs causes some warnings, and is generally just unclean. They use different release naming and repositories, so should just have separate updates files to track them (they're already separate on the server, they were just being copied from the same source file in the module). While here, remove the label and suite parameters from the Debian reprepro distribution templates, as they're unnecessary and potentially confusing (job nodes should never be relying on the suite names as they change at the next release). Also allow signatures from subkeys of the listed keys to be sufficient to verify the debian-security mirror's release files, like we do for the debian mirror. Change-Id: Id0ff476864f936bbd7c4637f3dc9e2c219c6e465
7 lines
170 B
Plaintext
7 lines
170 B
Plaintext
Name: debian-security
|
|
Method: http://security.debian.org/
|
|
Suite: */updates
|
|
Architectures: amd64 arm64
|
|
GetInRelease: no
|
|
VerifyRelease: EDA0D2388AE22BA9+|4DFAB270CAA96DFA+
|