On Wed, May 26, 2021, 9:45 AM Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote:
> On 5/13/21 2:36 AM, Steve Coleman wrote: > > > > > > On Wed, May 12, 2021, 5:52 PM Ulrich Windl > > <ulrich.wi...@rz.uni-regensburg.de > > <mailto:ulrich.wi...@rz.uni-regensburg.de>> wrote: > > > > On 4/30/21 1:31 AM, Andrew David Wong wrote: > > > Dear Qubes Community, > > > > > > Fedora 32 is scheduled to reach EOL (end-of-life [1]) on > 2021-05-25. > > > > I have a question on > > https://www.qubes-os.org/doc/template/fedora/upgrade/ > > <https://www.qubes-os.org/doc/template/fedora/upgrade/>: > > > > Towards the end of the update procedure "Detailed instructions for > > standard Fedora TemplateVMs" there is the command > > [user@dom0 ~]$ sudo dnf remove qubes-template-fedora-<old> > > > > However I wonder: I did not install a fedora-<new> template per > > instructions, and I wonder about this asymmetry. > > > > > > When you installed Qubes the default templates were installed for you. > > Because the fedora-32 came onto your system as an rpm it can only be > > removed by removing that rpm. To remove it, if you wish, you need to > > change all AppVMs to use some other template, to remove any qubes > > dependencies, then you remove the rpm. > > > > If you want to see all the default rpm templates you can do: "dom0> rpm > > -qa | grep qubes-template". Those templates need to be removed via dnf > > "rpm -qa qubes-template\*" might be a bit more efficient. ;-) > > > or rpm rather than just deleting it from the qube-manager or the qvm-* > > command line tool. When you clone a template it will not have an rpm > > file associated with it, so it can be removed easily using qube-manager. > > > > I always clone all the rpm templates then remove the rpm's, and then > > rename the clones to the name I actually want. If I ever need a fresh > > copy I can always reinstall the rpm and clone it to start over. > > So cloning actually duplicates the rpm-installed template so it's safe > to remove the RPM package afterwards? > Yes, it's safe. There are no rpm dependencies to prevent it's removal. You just need to be sure no AppVM anywhere on your system is currently using it. As long as no templates exist using the default name it's simple to reinstall from rpm to grab a pristine unmodified copy whenever you need one. Cloning it merely copies the template contents to a new template name that is not controlled by any rpm. The new clone can be backed up and restored like any normal vm and can be quickly removed as long as it has no Qubes AppVM dependencies using it. > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ5FDnjwY8tgWtsbgYPOiMimd529teSgsz_PgW7f6%3Doh4GfXUQ%40mail.gmail.com.
