tests: use ninja-build if ninja is not available#6544
tests: use ninja-build if ninja is not available#6544martinpitt merged 1 commit intosystemd:masterfrom
Conversation
This makes the tests work on CentOS, which currently has ninja-build only.
|
In https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-pitti-systemd-semaphore/xenial/amd64/s/systemd-upstream/20170806_031405_df843@/log.gz I've found the following: . I have run the tests on |
|
In https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/tests/upstream#n14 I see the following comment: # modify the image build scripts to install systemd from the debs instead of
# from a "make/ninja install" as we don't have a built tree here. Also call
# systemd-nspawn from the system., so it seems that |
|
@martinpitt, I've created the patch where |
|
Patch looks good, but I'll wait for @martinpitt to comment how he want to handle the ubuntu side. |
This should be merged and enabled after systemd/systemd#6544 is merged.
This makes the tests work on CentOS, which currently has ninja-build only.
This makes the tests work on CentOS, which currently has ninja-build only.
_ninja_bin was added in systemd/systemd#6544 in order to make the tests work on CentOS. As we don't actually do a "ninja install" and ninja is not available, replace the check with a dummy value.
This makes the tests work on CentOS, which currently has ninja-build only.