Re: sbuild --chroot-mode=autopkgtest: How to get an interactive shell?

[Christian Kastner <ckk@debian.org>]

On 2020-09-07 08:39, Paul Gevers wrote:
> I don't know. autopkgtest has an option to request interactive shell:
> either --shell or --shell-fail.

Ha, I wasn't aware of this.

Using in with autopkgtest-virt-qemu, I get:

> You can now log into the VM through the serial terminal.
> Depending on which terminal program you have installed, you can use one of
> 
>     ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 10022 user@localhost
>     minicom -D unix#/home/christian/tmp/autopkgtest-qemu.m2tkfqk3/ttyS0
>     nc -U /home/christian/tmp/autopkgtest-qemu.m2tkfqk3/ttyS0
>     socat - UNIX-CONNECT:/home/christian/tmp/autopkgtest-qemu.m2tkfqk3/ttyS0
> 
> The tested source package is in /tmp/autopkgtest.KxWQJt/build.kjz/src
> 
> Press Enter to resume running tests.

Which supports my suspicion that the "proper" way to connect to the VM
is from the outside.

I'm not sure sbuild can be hacked to handle this case, as "runcmd" seems
to be used for all command execution.

It might be possible, however, to hack runcmd. For example, by adding a
--shell option that exec's one of the above methods of connecting to the
VM.

I'll fool around a bit, and see what results I get.