[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debci: how are 'experimental' and '-backports' environments handled?



Hi Christian,

On 05-08-2023 10:09, Christian Kastner wrote:
if I read the source correctly, then tests will use extra APT sources
from extra_apt_source_list.yaml [1]. 'experimental' would be an example
for that; likewise 'bookworm-backports'.

Those are *extra* archives available to autopkgtest's --add-apt-release. As in, the main archives we support are unstable, testing, stable and oldstable, and users can *add* one or more extra archives to one of those suites.

However, `debci localtest -s experimental` fails because it looks for an
image with the name 'experimental[...]', rather than 'unstable[...].

Because experimental is typically *added* to unstable.

How is this accomplished on ci.debian.net?

If you want to add additional archives, you can tick the bock in the self service page or add it via the API.

Intuitively, I'd just map/symlink these environments, but I couldn't
find any code to that end. And this would also have to be accounted for
in debci-update-worker.

debci-update-worker just updates the base suites. It's autopkgtest with --add-apt-release that does the magic.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: