[Qubes 4.0] Updating migrated templates from 3.2

[p.o.m...@gmail.com]

Hello,

I'm trying to get a fedora-25 template from Qubes 3.2 updated to Fedora 26 on Qubes 4.0. This template has a variety of packages already installed and I thought it would be easier to bring this forward to Fedora 26 rather than trying to reinstall everything on the default fedora-26 template.

It appears that the template update process is very different in Qubes 4.0, with networking changes and a number of repo updates. Is there any documentation on how to get this to work, such as what files need to be updated and what configuration settings tweaked?

Thanks,
- Paul M

[awokd]

Usually you're going to be further ahead starting from the fedora-26
provided with 4.0 and re-adding packages, but if you want to try upgrading
from 3.2 25, search this mailing list. I think others have attempted it,
but don't believe there's an "officially supported" procedure.

[p.o.m...@gmail.com]

I mainly ask the question because I already had templates that were up-to-date in terms of software packages, so there's no real reason to be starting over there.

It would be nicer to be able to update whatever they need for their Qubes backend and keep the template going.

This is especially true for templates that are built on other distros, like Arch or Ubuntu. I have to imagine the larger Qubes community will be looking for some way to migrate existing templates in a more seamless manner.

[cooloutac]

yes you can do that but you have to give it a non default name. If its the same name as default template then you will most likely run into problems.

I have had no problem restoring cloned templates from 3.2 into 4.0. But I have not tried to restore any appvms or templatevms with default names.

[cooloutac]

I'm sorry actually i have restored appvms with default names, just not templates. only cloned ones with non default names.

[p.o.m...@gmail.com]

That's odd. It doesn't work for me with templates that I have with non-default names. That's why I was asking this question.

There's no instructions out there about which qubes packages need updating or installing, nor are there instructions about how to update the Qubes repositories.

This is the kind of thing that I was asking about. Without knowing all that info it doesn't matter if the template has a non-default name or not.

[cooloutac]

hmm maybe i'm wrong then. In my fedora 26 clone. there is a file called qubes-r4.repo contains :

[qubes-vm-r4.0-current-testing]
name = Qubes OS Repository for VM (updates-testing)
baseurl = https://yum.qubes-os.org/r4.0/current-testing/vm/fc$releasever
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4-primary
skip_if_unavailable=False
gpgcheck = 1
enabled=0

[qubes-vm-r4.0-security-testing]
name = Qubes OS Repository for VM (security-testing)
baseurl = https://yum.qubes-os.org/r4.0/security-testing/vm/fc$releasever
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4-primary
skip_if_unavailable=False
gpgcheck = 1
enabled=1

[qubes-vm-r4.0-unstable]
name = Qubes OS Repository for VM (unstable)
baseurl = http://yum.qubes-os.org/r4.0/unstable/vm/fc$releasever
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4-unstable
gpgcheck = 1
enabled=0

[cooloutac]

You have to change it to https if using sys-whonix updatevm for the templates.

[cooloutac]

[qubes-vm-r4.0-current]
name = Qubes OS Repository for VM (updates)
baseurl = https://yum.qubes-os.org/r4.0/current/vm/fc$releasever