279cb28e34
Each Ubuntu and Debian release get a separate independent repository (though served from the same AFS volume) which means we need to explicitly add each release to reprepro when they occur. Now that we've switched to Noble as our default nodeset it has become apparent we did not do this for Noble's Docker packages. Go ahead and add a debian docker noble mirror. Note that reprepro has a *.log logrotate rule for all logs produced by reprepro so we don't need to explicitly add a rule for the new log file. We also don't need a new volume in AFS as a single deb-docker volume is used for all of these repo mirrors. We pin the tox-linters and buildset-registry jobs to jammy because they don't currently run on Noble. Linters faile because we need to use newer hacking whcih we'll do in a followup that cleans up new errors and the registry fails due to the issue we are trying to fix in this very change (need docker packages for noble). Change-Id: I289f19a11539b490c3b7327d01d517948b95e072 |
||
|---|---|---|
| .. | ||
| files | ||
| tasks | ||
| README.rst | ||
reprepo
Install reprepo configuration for configuring various repositories.
Note that this role is only intended to be called from the
mirror-update role.