Change in osmo-ci[master]: repo-install-test: disable ProtectHome option

Attention is currently required from: osmith. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/30471 ) Change subject: repo-install-test: disable ProtectHome option ...................................................................... Patch Set 2: Code-Review+1 (1 comment) Patchset: PS2: I'm in general quite sceptic. We're replacing docker with podman as supposedly we can run more thngs there without container specific hacks. But it looks like we're adding various new workarounds here, so I'm wondering if this really is the way to go. Maybe we simply want to run those tests in a qemu-kvm virtual machine, after all? we could always start from the same clean disk image, with COW for the changes done by the job. And once it's completed, we delete the COW and the next execution starts from clean rootfs again. -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/30471 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: I394918fc61de36acce65ffb33defcb8fc21801c4 Gerrit-Change-Number: 30471 Gerrit-PatchSet: 2 Gerrit-Owner: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: msuraev <msuraev(a)sysmocom.de> Gerrit-Attention: osmith <osmith(a)sysmocom.de> Gerrit-Comment-Date: Mon, 05 Dec 2022 17:45:37 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Gerrit-MessageType: comment