Hello Steve,
Am Fri, 12 Apr 2019 22:28:21 -0700 schrieb Steve Langasek <steve.langa...@canonical.com>: > Package sysvinit-core is not available, but is referred to by another package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > However the following packages replace it: > systemd-sysv > > autopkgtest [20:35:15]: test master-sysvinit-cron: -----------------------] > master-sysvinit-cron FAIL non-zero exit status 100 > [...] > > > (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/m/munin/20190412_204534_b9ff8@/log.gz) > > It seems to me this could be sidestepped by having the test declare a > dependency on sysvinit-core instead of installing it as part of the test, > and also using Restrictions: skip-not-installable. Thank you for this suggestion! After taking a quick look at my comments in the test scripts, I am afraid, that the test dependency may not work without further changes: https://salsa.debian.org/debian/munin/blob/debian/debian/tests/enable_sysvinit.inc#L8 I will take a closer look at this issue after the release of Buster. Cheers, Lars
