The documentation includes [a method to allow one Salsa job to use binary packages from another package's Salsa build job](https://salsa.debian.org/salsa-ci-team/pipeline/#using-automatically-built-apt-repository). This no longer works: the first package creates the aptly repository, but [the second package will not use it](https://salsa.debian.org/python-team/packages/actdiag/-/pipelines). The first failure is that apt no longer accepts `deb [trusted=yes]` with no key. However, after working around that with ```before_script: - apt-get install curl - curl -o /etc/apt/keyrings/blockdiag.gpg https://salsa.debian.org/python-team/packages/blockdiag/-/jobs/8357955/artifacts/raw/aptly/public-key.gpg - echo "deb [signed-by=/etc/apt/keyrings/blockdiag.gpg] https://salsa.debian.org/python-team/packages/blockdiag/-/jobs/8357955/artifacts/raw/aptly unstable main" | tee /etc/apt/sources.list.d/blockdiag.list - apt-get update ``` it still fails because before_script runs before entering the sbuild chroot, which resets these settings. If there is no easy way to actually fix this, I suggest removing it from the documentation.