testing/os-autoinst-distri-rocky
11
0
Fork 0
mirror of https://github.com/rocky-linux/os-autoinst-distri-rocky.git synced 2024-11-29 00:16:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Drop a couple of obsolete workarounds from _installer_build

Browse Source 
F28-era stuff.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2019-12-20 09:19:13 -08:00
parent 5be282c744
commit 20b16e9345
1 changed files with 1 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
tests/_installer_build.pm
View File

@ -8,19 +8,10 @@ sub run {
my $version = get_var("VERSION"); my $version = get_var("VERSION");
my $advortask = get_var("ADVISORY_OR_TASK"); my $advortask = get_var("ADVISORY_OR_TASK");
my $arch = get_var("ARCH"); my $arch = get_var("ARCH");
# we need lorax from u-t for f28 atm it seems assert_script_run "dnf -y install lorax", 90;
my $loraxcmd = "dnf -y ";
$loraxcmd .= "--enablerepo=updates-testing " if (get_var("VERSION") eq "28");
$loraxcmd .= "install lorax";
assert_script_run $loraxcmd, 90;
# this 'temporary file cleanup' thing can actually wipe bits of # this 'temporary file cleanup' thing can actually wipe bits of
# the lorax install root while lorax is still running... # the lorax install root while lorax is still running...
assert_script_run "systemctl stop systemd-tmpfiles-clean.timer"; assert_script_run "systemctl stop systemd-tmpfiles-clean.timer";
# dracut-fips doesn't exist any more; this breaks f28 builds as
# it *did* exist when f28 came out, so lorax tries to use
# dracut-fips from the frozen release repo with newer lorax from
# the updates repo which obsoletes it, and gets confused
assert_script_run 'sed -i -e "s,dracut-fips,,g" /usr/share/lorax/templates.d/99-generic/runtime-install.tmpl';
assert_script_run "mkdir -p /root/imgbuild"; assert_script_run "mkdir -p /root/imgbuild";
assert_script_run "pushd /root/imgbuild"; assert_script_run "pushd /root/imgbuild";
assert_script_run "setenforce Permissive"; assert_script_run "setenforce Permissive";