diskimage-builder/diskimage_builder/elements/yum/post-install.d/99-reset-yum-conf

#!/bin/bash

if [ ${DIB_DEBUG_TRACE:-1} -gt 0 ]; then
    set -x
fi
set -eu
set -o pipefail

if [[ -n ${DIB_YUM_DNF_CONTENTDIR:-''} ]]; then
  mv /etc/dnf/vars/contentdir.bak /etc/dnf/vars/contentdir
  sed -i -e 's,^#mirrorlist,mirrorlist,' -e 's,^baseurl,#baseurl,' /etc/yum.repos.d/*.repo
fi


if [[ ${YUM} =~ "dnf" ]]; then
    cfg=/etc/dnf/dnf.conf
    cachedir=/var/cache/dnf
else
    cfg=/etc/yum.conf
    cachedir=/var/cache/yum
fi

sed -i "/^keepcache/c\keepcache=0" $cfg
sed -i "/^cachedir/c\cachedir=${cachedir}" $cfg
Reset yum configuration in post-install.d When using the yum element, we should reset the changes we've made to /etc/yum.conf during post-install.d. Otherwise, this build time configuration is propagated into booted instances. Change-Id: I1eea586ca0fefe9bc0cf91fedefcbd141a536fa2 2014-09-12 00:59:50 +00:00			`#!/bin/bash`

Standarise tracing for scripts There is a wide variety of tracing options through the various shell scripts. Some use "set -eux", others explicity set xtrace and others do nothing. There is a "-x" option to bin/disk-image-create but it doesn't flow down to the many scripts it calls. This adds a global integer variable set by disk-image-create DIB_DEBUG_TRACE. All scripts have a stanza added to detect this and turn on tracing. Any other tracing methods are rolled into this. So the standard header is --- if [ "${DIB_DEBUG_TRACE:-0}" -gt 0 ]; then set -x fi set -eu set -o pipefail --- Multiple -x options can be specified to dib-create-image, which increases the value of DIB_DEBUG_TRACE. If script authors feel their script should only trace at higher levels, they should modify the "-gt" value. If they feel it should trace by default, they can modify the default value also. Changes to pachset 16 : scripts which currently trace themselves by default have retained this behaviour with DIB_DEBUG_TRACE defaulting to "1". This was done by running [1] on patch set 15. See the thread beginning at [2] dib-lint is also updated to look for the variable being matched. [1] https://gist.github.com/ianw/71bbda9e6acc74ccd0fd [2] http://lists.openstack.org/pipermail/openstack-dev/2014-November/051575.html Change-Id: I6c5a962260741dcf6f89da9a33b96372a719b7b0 2014-09-04 04:56:29 +00:00			`if [ ${DIB_DEBUG_TRACE:-1} -gt 0 ]; then`
			`set -x`
			`fi`
			`set -eu`
Reset yum configuration in post-install.d When using the yum element, we should reset the changes we've made to /etc/yum.conf during post-install.d. Otherwise, this build time configuration is propagated into booted instances. Change-Id: I1eea586ca0fefe9bc0cf91fedefcbd141a536fa2 2014-09-12 00:59:50 +00:00			`set -o pipefail`

several random fixes need to rebase 2023-11-21 21:28:47 +00:00			`if [[ -n ${DIB_YUM_DNF_CONTENTDIR:-''} ]]; then`
i don't even know at this point 2023-11-22 01:56:09 +00:00			`mv /etc/dnf/vars/contentdir.bak /etc/dnf/vars/contentdir`
			`sed -i -e 's,^#mirrorlist,mirrorlist,' -e 's,^baseurl,#baseurl,' /etc/yum.repos.d/*.repo`
several random fixes need to rebase 2023-11-21 21:28:47 +00:00			`fi`

make it work for rocky 2023-11-15 18:43:48 +00:00
i don't even know at this point 2023-11-22 01:56:09 +00:00			`if [[ ${YUM} =~ "dnf" ]]; then`
Work around yum/dnf differences Some minor workarounds for Fedora >= 22 where dnf is the default package manager. The changes are documented on the Fedora release notes https://fedoraproject.org/wiki/Changes/ReplaceYumWithDNF Change-Id: I7d7d6f5d294980dcb217d6190a1efd9e0bbea9a6 2015-05-27 04:53:04 +00:00			`cfg=/etc/dnf/dnf.conf`
Reset yum/dnf cache to correct location Make sure we reset the yum/dnf cache to /var/cache/${YUM}, not just /var/cache/yum This was resulting in the F22 fedora-minimal image being larger than the base-image. Because F22 fedora-minimal does some installs with dnf when bootstrapping the chroot before we set "cachedir=" to the bind-mounted external cache, we have "/var/cache/dnf" created and and populated with the package meta-data, etc. When we globally point dnf to /var/cache/yum here, we effectively orphan the /var/cache/dnf created in those first steps. dnf doesn't care, but we end up with two copies of all the package metadata, etc in "/var/cache/dnf" & "/var/cache/yum". This also cleans up the sed a bit, by just replacing the lines. Change-Id: Icc98fe30c34cb941aed4b987647ab67ac34af15a 2015-10-09 04:43:19 +00:00			`cachedir=/var/cache/dnf`
Work around yum/dnf differences Some minor workarounds for Fedora >= 22 where dnf is the default package manager. The changes are documented on the Fedora release notes https://fedoraproject.org/wiki/Changes/ReplaceYumWithDNF Change-Id: I7d7d6f5d294980dcb217d6190a1efd9e0bbea9a6 2015-05-27 04:53:04 +00:00			`else`
			`cfg=/etc/yum.conf`
Reset yum/dnf cache to correct location Make sure we reset the yum/dnf cache to /var/cache/${YUM}, not just /var/cache/yum This was resulting in the F22 fedora-minimal image being larger than the base-image. Because F22 fedora-minimal does some installs with dnf when bootstrapping the chroot before we set "cachedir=" to the bind-mounted external cache, we have "/var/cache/dnf" created and and populated with the package meta-data, etc. When we globally point dnf to /var/cache/yum here, we effectively orphan the /var/cache/dnf created in those first steps. dnf doesn't care, but we end up with two copies of all the package metadata, etc in "/var/cache/dnf" & "/var/cache/yum". This also cleans up the sed a bit, by just replacing the lines. Change-Id: Icc98fe30c34cb941aed4b987647ab67ac34af15a 2015-10-09 04:43:19 +00:00			`cachedir=/var/cache/yum`
Work around yum/dnf differences Some minor workarounds for Fedora >= 22 where dnf is the default package manager. The changes are documented on the Fedora release notes https://fedoraproject.org/wiki/Changes/ReplaceYumWithDNF Change-Id: I7d7d6f5d294980dcb217d6190a1efd9e0bbea9a6 2015-05-27 04:53:04 +00:00			`fi`

Reset yum/dnf cache to correct location Make sure we reset the yum/dnf cache to /var/cache/${YUM}, not just /var/cache/yum This was resulting in the F22 fedora-minimal image being larger than the base-image. Because F22 fedora-minimal does some installs with dnf when bootstrapping the chroot before we set "cachedir=" to the bind-mounted external cache, we have "/var/cache/dnf" created and and populated with the package meta-data, etc. When we globally point dnf to /var/cache/yum here, we effectively orphan the /var/cache/dnf created in those first steps. dnf doesn't care, but we end up with two copies of all the package metadata, etc in "/var/cache/dnf" & "/var/cache/yum". This also cleans up the sed a bit, by just replacing the lines. Change-Id: Icc98fe30c34cb941aed4b987647ab67ac34af15a 2015-10-09 04:43:19 +00:00			`sed -i "/^keepcache/c\keepcache=0" $cfg`
			`sed -i "/^cachedir/c\cachedir=${cachedir}" $cfg`