On 2026-02-05 13:43, Antonio Terceiro wrote:
Control: tag -1 + confirmed
Thanks for the bug report
On Wed, Feb 04, 2026 at 09:47:53PM +0100, Drew Parsons wrote:
It would be useful to be able to "Request Test" forcing installation
of the indicated packages. This could be a separate or additional
option to simply pinning the packages.
I'm assuming this would already be possible via --setup-commands. Can
you work out what the autopkgtest call would look like in this case?
You're right, as far as autopkgtest goes, --setup-commands can manage it
e.g.
sudo autopkgtest -B --setup-commands="apt-get install ${PKGLIST}"
I needed sudo in the context of testing on my own command line in order
for apt-get to be able to perform the installation. I don't know if it
would be needed in the context of debci.
Locally I tested autopktest with `-- null` i.e. I didn't run autopkgtest
through a chroot. But I don't think this point is relevant for debci.
I ran the install step with apt-get rather than apt, since apt provides
extra interactive user interfacing like progress counting. Nice for
interactive runs but not useful for CI testing, and `apt install` would
need to add -y, as `apt install -y` to skip pass the interactive user
communication. apt-get is simpler. But you'd want it consistent with
whatever the commands is when managing pinning.
PKGLIST needs to be set of course
e.g. PKGLIST="libopenblas-openmp-dev/experimental
libopenblas-dev/experimental"
