{{Box|text= '''1.''' Enable qubes-templates-community-testing repository. View the [https://github.com/QubesOS/qubes-qubes-release/blob/87a279b64c37e7bb3ae7d24aa413b33734da8856/qubes-templates.repo Qubes Templates .repo] file. {{CodeSelect|code= cat /etc/yum.repos.d/qubes-templates.repo }} '''2.''' Ensure the file contains [qubes-templates-community-testing]. The following text should be included.

[qubes-templates-community-testing]
name = Qubes Community Templates repository
#baseurl = https://yum.qubes-os.org/r$releasever/templates-community-testing
metalink = https://yum.qubes-os.org/r$releasever/templates-community-testing/repodata/repomd.xml.metalink
enabled = 0
fastestmirror = 1
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-$releasever-templates-community

'''3.''' Fix any missing sections. If the [qubes-templates-community-testing] section is missing, then the user has probably already modified the file. In this case dnf Which is invoked by qubes-dom0-update. preserves user changes by saving updates to /etc/yum.repos.d/qubes-templates.repo.rpmnew Note the file extension .repo.rpmnew. instead of overwriting the file. Since the .repo.rpmnew file is ignored by qubes-dom0-update, the .repo file must be manually updated. Either: * Manually add the changes from .repo.rpmnew to the .repo file; or * Overwrite the .repo file with the .repo.rpmnew file: ** {{CodeSelect|code= sudo cp /etc/yum.repos.d/qubes-templates.repo.rpmnew /etc/yum.repos.d/qubes-templates.repo }} ** And then manually add back necessary changes. If the command fails because /etc/yum.repos.d/qubes-templates.repo.rpmnew does not exist, then the user probably has [qubes-templates-community-testing] already. }}