In dom0 I set the “enabled” value to ‘1’ in /etc/yum.repos.d/qubes-templates.repo for both
qubes-templates-itl-testing and templates-community-testing. I updated dom0.
When I run qvm-template-gui I do not see any additional templates listed from these repo. What am I doing wrong?
Running fresh install Q4.1rc3
Does running
sudo qubes-dom0-update --enablerepo=qubes-templates-itl-testing
sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing
before running qvm-template-gui helps? Or to restart Qubes? I see all the templates.
Thanks for the reply. I have executed both these commands and also rebooted. Qubes Template Manager still does not show the community/testing repo.
Running fresh install Q4.1rc3. What about you?
I am running 4.1 rc2 updated (which should be upgraded to rc3 that way), Are correspondent metalinks uncommented in qubes-templates.repo? Other then that, I have an idea. Here’s the content of my qubes-templates.repo:
name = Qubes Templates repository
#baseurl = https://yum.qubes-os.org/r$releasever/templates-itl
#baseurl = http://yum.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r$releasever/templates-itl
metalink = https://yum.qubes-os.org/r$releasever/templates-itl/repodata/repomd.xml.metalink
enabled = 1
fastestmirror = 1
metadata_expire = 7d
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-$releasever-primary
[qubes-templates-itl-testing]
name = Qubes Templates repository
#baseurl = https://yum.qubes-os.org/r$releasever/templates-itl-testing
#baseurl = http://yum.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r$releasever/templates-itl-testing
metalink = https://yum.qubes-os.org/r$releasever/templates-itl-testing/repodata/repomd.xml.metalink
enabled = 1
fastestmirror = 1
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-$releasever-primary
[qubes-templates-community]
name = Qubes Community Templates repository
#baseurl = https://yum.qubes-os.org/r$releasever/templates-community
#baseurl = http://yum.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r$releasever/templates-community
metalink = https://yum.qubes-os.org/r$releasever/templates-community/repodata/repomd.xml.metalink
enabled = 1
fastestmirror = 1
metadata_expire = 7d
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-$releasever-templates-community
[qubes-templates-community-testing]
name = Qubes Community Templates repository
#baseurl = https://yum.qubes-os.org/r$releasever/templates-community-testing
#baseurl = http://yum.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r$releasever/templates-community-testing
metalink = https://yum.qubes-os.org/r$releasever/templates-community-testing/repodata/repomd.xml.metalink
enabled = 1
fastestmirror = 1
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-$releasever-templates-community
The contents of my qubes-templates.repo is exactly the same as yours.
On a side note, I noticed when I installed rc2 the templates from the testing/community repo showed fine in qvm-template-gui. Now on a fresh install of rc3 they do not show.
Oh, that probably makes if suitable for a Github issue…
I also have the same issue with a fresh install rc3
Even manually enabling the testing repository in qubes-templates.repo does not change any results.
Thankfully I have a backup of my fedora-35-minimal that worked in rc2 I was able to import.
I am not sure what else to try.
Maybe to rename topic’s subject to something more attracting to developers - Enabling community and testing template repos in Qubes-OS v4.1 rc3 doesn’t work, for example…?
I am not OP but I am happy to make a new post and/or github issue about this.
I do not have a github account but it would certainly be appreciated if someone could post an issue since this is obviously a real bug 
Posted
Feel free to add things I have missed or if I need to clarify anything just let me know.
I also confirm this problem
This is a known issue in recent builds.
Already on GitHub and fix in pipeline.
Can confirm fix works
https://github.com/QubesOS/qubes-core-admin-client/pull/204
Ran
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
rebooted and I can list testing templates. Thank you!