Running 4.2.3, upgraded from 4.2.2. Templates are fedora-39.
Qubes update states that fedora-39 templates are EOL and that I shall install new templates.
fedora-40-xfce is in the qubes-templates-itl-testing repository. For best stability, should I upgrade to it even it is in the testing repo? What’s the best practice.
Did a manual upgrade of fedora-39-sys to 40 and it worked fine.
It’s available in the stable repo as well:
https://yum.qubes-os.org/r4.2/templates-itl/rpm/qubes-template-fedora-40-xfce-4.2.0-202409070311.noarch.rpm
I guess you have enabled templates-testing repository in the Qubes Global Config and the Qubes Template Manager only shows you the latest template version which is from the templates-testing repository.
UPD:
I’ve checked and Qubes Template Manager is displaying fedora-40-xfce for both stable and testing repositories.
So I guess your question was which template to install: from stable or from testing repository? For best stability it’s better to install it from stable repository.
deleted message
Thank you. What I find deviate is that in my Qubes global config I have only checked “Enable stable updates only”.
“Official testing templates” and “Community templates” are unchecked.
Anyway, the only “fedora-40-xfce” I find in the template manger is from the qubes-templates-itl-testing repository (which I maybe should not see at all?).
Should I do the manual update and assume it uses the stable and not testing repo?
It seems to be this issue:
What’s the content of this file in dom0?
/etc/qubes/repo-templates/qubes-templates.repo
I’m having the same problem and that read-only file lists both testing repositories even though they are unchecked in the Global Settings GUI.
[qubes-templates-itl]
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/qubes/repo-templates/keys/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 = 0
fastestmirror = 1
gpgcheck = 1
gpgkey = file:///etc/qubes/repo-templates/keys/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 = 0
fastestmirror = 1
metadata_expire = 7d
gpgcheck = 1
gpgkey = file:///etc/qubes/repo-templates/keys/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 = 0
fastestmirror = 1
gpgcheck = 1
gpgkey = file:///etc/qubes/repo-templates/keys/RPM-GPG-KEY-qubes-$releasever-templates-community
Is you dom0 update proxy a standalone qube?
Try to restart your dom0 update proxy to flush the repository cache.
sys-firewall is the dom0 update proxy. Have rebooted the PC multiple times without that helping. Any other restart I should try?
sys-net is the Default update proxy.
That should be enough to reset the cache.
I guess the templates repository info is stored somewhere else as well, but I don’t know where to look for it.
So for clarity, if in our Qubes Template manager, fedora-40-xfce is shown as being in the qubes-templates-itl repository, we should consider it as having been marked as stable by the Qubes OS maintainers team and we can install it?
Yes.
From a user’s perspective, what is the best solution until this is fixed? Should I install and use the testing template?
What’s the output of these commands in dom0?
qvm-template repolist
qvm-template --repoid qubes-templates-itl list
Also you can try to install it like this:
qvm-template --repoid qubes-templates-itl install fedora-40-xfce
Or:
qvm-template --repoid qubes-templates-itl --enablerepo qubes-templates-itl install fedora-40-xfce
The only repos listed by ‘qvm-template repolist’ are:
qubes-templates-community
qubes-templates-itl
‘qvm-template --repoid qubes-templates-itl list’ does list fedora-40-xfce.
So in qvm-template repolist you have only qubes-templates-community and qubes-templates-itl repos, but in GUI Qubes Template Manager you have testing repos as well?
Or you have only testing repos without stable repos in GUI Qubes Template Manager?
I only have non-testing repos in qvm-template repolist, but there are testing repos in /etc/qubes/repo-templates/qubes-templates.repo and I have testing templates in the GUI template manager where the only fedora-40-xfce template is from testing.
Are they enabled (enabled = 1)?
Actually only the non-testing templates are enabled = 1 and the testing templates are enabled = 0. So everything seems to be correct except I have testing templates in the GUI template manager which prevents me from installing stable fedora-40-xfce.
Then I guess it’s an issue with GUI Qubes Template Manager specifically.
Use the qvm-template CLI tool to mange the stable templates until the github issue with GUI Qubes Template Manager linked previously is fixed.