Control: reassign -1 lxc-templates Control: retitle -1 consider adding security repos by default Control: affects -1 debci autopkgtest
Hi all, On 05-11-2023 03:41, Santiago Ruano Rincón wrote:
Is there any reason why `debci setup ...` doen't configure the security
repostories inside the lxc containers? This is the sources.list of a
just created autopkgtest-bookworm-amd64 container:
deb http://deb.debian.org/debian bookworm main contrib non-free
non-free-firmware
deb-src http://deb.debian.org/debian bookworm main contrib non-free
non-free-firmware
deb http://deb.debian.org/debian-debug bookworm-debug main contrib
non-free non-free-firmware
deb-src http://deb.debian.org/debian-debug bookworm-debug main contrib
non-free non-free-firmware
As debci with the lxc backend just uses lxc-templates to set-up the containers, I think this is something for lxc-templates to consider.
Having said that, I'm unsure if *I* (with my ci.debian.net maintainer and my Release Team member hat on) would want that. For lxc users it's easier to *add* repositories than it is to remove them for the use case where you don't want the security archive installed (e.g. for Release Team's testing of proposed-updates against stable). So, for ci.debian.net I'd want an easy way to opt-out of the security archive in case it gets added by default.
debci supports the user (both via the API as well as via the self-service) to easily add repositories once debci is configured to support those additional repositories (as ci.debian.net does).
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
