94ad759b2e
As a follow-on to Ic33bca431ae19b44e5bc2938de425cc68785b331 ... (reprepro configuration really is quite inscrutable outside "try it and see if it works") The update is just called "debian-security", no codename. We want to use the debian-security key to validate the gpg signatures, update that. Use the "updates" suite, which seems to be where debian-security is Add the symlink for mirror Change-Id: Ice2a06f4274cdad766f427df70d9fe3e92f62e8c |
||
---|---|---|
.. | ||
ceph-mirror-gpg-key.asc | ||
debian-ceph-hammer-updates | ||
debian-ceph-jewel-updates | ||
debian-ceph-luminous-updates | ||
debian-ceph-mimic-updates | ||
debian-docker-updates | ||
debian-security-updates | ||
debian-stretch-mirror-gpg-key.asc | ||
debian-stretch-security-mirror-gpg-key.asc | ||
debuntu-updates | ||
docker-mirror-gpg-key.asc | ||
mariadb-mirror-gpg-key.asc | ||
mariadb-mirror-new-gpg-key.asc | ||
puppetlabs-debs | ||
puppetlabs-mirror-gpg-key.asc | ||
reprepro-mirror-update.sh | ||
ubuntu-cloud-archive-gpg-key.asc | ||
ubuntu-cloud-archive-updates |