Fix dnf update installing netavark/aardvark-dns

These packages should _never_ be pre-installed in the CI images for testing in the netavark & aardvark-dns repositories. Ensure they aren't brought in by a package update in addition to the install. Signed-off-by: Chris Evich <[email protected]>
containers · Jul 14, 2022 · 1b2ff3a · 1b2ff3a
1 parent c4b1e45
commit 1b2ff3a
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/cache_images/fedora-netavark_packaging.sh b/cache_images/fedora-netavark_packaging.sh
@@ -61,13 +61,17 @@ INSTALL_PACKAGES=(\
     zip
 )
 
+# Downstream users of this image are specifically testing netavark & aardvark-dns.
+# They will take care of either building or obtaining the relelvent binaries
+# at runtime.  Similar for cargo and rust.  Ensure these are absent, to allow
+# runtime install of newer bits.
 EXARG="--exclude=netavark --exclude=aardvark-dns --exclude=cargo --exclude=rust"
 
 msg "Installing general build/test dependencies"
 bigto $SUDO dnf install -y $EXARG "${INSTALL_PACKAGES[@]}"
 
-# It was observed in F33, dnf install doesn't always get you the latest/greatest
-lilto $SUDO dnf update -y
+# It was observed in F33, dnf install doesn't always get you the latest/greatest.
+lilto $SUDO dnf update -y $EXARG
 
 msg "Initializing upstream rust environment."
 export CARGO_HOME="/var/cache/cargo"  # must match .cirrus.yml in netavark repo