debian: freedombox 24.19 migration to testing delayed

As seen on https://tracker.debian.org/pkg/freedombox, freedombox 24.19 has not yet migrated to testing, due to a "Test in progress" result for autopkgtest on the s390x architecture. The build results and logs can be obtained at https://ci.debian.net/packages/f/freedombox/testing/s390x/.

The test log shows that test command1 (listing FreedomBox modules) was completed successfully. However when it is preparing the testbed for test command2 (run py.test), there is an apt error "Could not resolve 'deb.debian.org'". Note that freedombox, and therefore systemd-resolved, was installed during the testbed preparation for test command1.

I added some debugging statements to the tests (run locally) to see more details. This shows that /etc/resolv.conf is changing in-between test command1 and test command2. I think this suggests that there could be a race condition between systemd-resolved starting up, and the test commands being run. We could consider adding a delay that checks if systemd-resolved has finished starting before continuing the test.

autopkgtest [14:28:37]: test command1: ls -al /etc/resolv.conf; cat /etc/resolv.conf; plinth --list-apps 2> /dev/null
autopkgtest [14:28:37]: test command1: [-----------------------
lrwxrwxrwx 1 root root 39 Sep 18 18:27 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search .

autopkgtest [14:29:31]: test command2: ls -al /etc/resolv.conf; cat /etc/resolv.conf; PYTHONPATH='/usr/lib/python3/dist-packages/' py.test-3 -p no:cacheprovider --cov=plinth --cov-report=html:debci/htmlcov --cov-report=term
autopkgtest [14:29:31]: test command2: [-----------------------
lrwxrwxrwx 1 root root 39 Sep 18 18:27 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search .