Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-12-25 07:19:33 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'patch-2' of https://github.com/qtpies/qubes-doc into qtpies-patch-2

Browse Source
This commit is contained in:
Andrew David Wong 2020-08-16 03:13:40 -05:00
commit a51ccb4262
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
4 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
user/managing-os/debian/debian-upgrade.md
View File

@ -1,6 +1,6 @@
---
layout: doc
title: Upgrading Debian TemplateVMs
title: In-place upgrade of Debian TemplateVMs
permalink: /doc/template/debian/upgrade/
redirect_from:
- /doc/template/debian/upgrade-8-to-9/
@ -12,6 +12,8 @@ redirect_from:
# Upgrading Debian TemplateVMs
[Should I upgrade using a fresh installation or an in-place upgrade?][Upgrading Debian TemplateVMs]
This page provides instructions for performing an in-place upgrade of an installed [Debian TemplateVM].
If you wish to install a new, unmodified Debian TemplateVM instead of upgrading a template that is already installed in your system, please see the [Debian TemplateVM] page instead.

4
user/managing-os/debian/debian.md
View File

@ -48,9 +48,9 @@ Please see [Updating software in TemplateVMs].
## Upgrading
Upgrading from your current release to a newer release.
There are two ways to upgrade a TemplateVM. The easiest way is to [install] the new Debian TemplateVM next to the Debian TemplateVM you are currently using. Then redo all desired template modifications, and switch everything that was set to the old template to the new template.To make this process as efficient as possible, document modifications to your TemplateVMs in a text file. If you do not have this documentation yet, open a terminal in the old Debian TemplateVM, and use the `history` command. (There is currently no other way to gain a list of explicitly installed packages. Methods like `apt list --installed`, `dpkg -l` and `aptitude search '~i!~M'` all include packages that have been installed as dependencies.)
Please see [Upgrading Debian TemplateVMs].
You can also do an in-place upgrade of an installed Debian TemplateVM. Please see [Upgrading Debian TemplateVMs].
## Release-specific notes

10
user/managing-os/fedora/fedora-upgrade.md
View File

@ -1,6 +1,6 @@
---
layout: doc
title: Upgrading Fedora TemplateVMs
title: In-place upgrade of Fedora TemplateVMs
permalink: /doc/template/fedora/upgrade/
redirect_from:
- /doc/template/fedora/upgrade-26-to-27/
@ -23,6 +23,8 @@ redirect_from:
# Upgrading Fedora TemplateVMs
[Should I upgrade using a fresh installation or an in-place upgrade?][Upgrading Fedora TemplateVMs]
This page provides instructions for performing an in-place upgrade of an installed [Fedora TemplateVM].
If you wish to install a new, unmodified Fedora TemplateVM instead of upgrading a template that is already installed in your system, please see the [Fedora TemplateVM] page instead.
@ -194,11 +196,7 @@ In this case, you have several options:
However, you may end up having to increase the disk image size anyway (see previous option).
3. Do the upgrade in parts, e.g., by using package groups.
(First upgrade `@core` packages, then the rest.)
4. Do not perform an in-place upgrade.
Instead, simply download and install a new template package, then redo all desired template modifications.
Here are some useful messages from the mailing list that also apply to TemplateVM management and migration in general from
[Marek](https://groups.google.com/d/msg/qubes-users/mCXkxlACILQ/dS1jbLRP9n8J) and
[Jason M](https://groups.google.com/d/msg/qubes-users/mCXkxlACILQ/5PxDfI-RKAsJ).
4. Do not perform an in-place upgrade, see [Upgrading Fedora TemplateVMs].
[Fedora TemplateVM]: /doc/templates/fedora/

4
user/managing-os/fedora/fedora.md
View File

@ -40,9 +40,9 @@ Please see [Updating software in TemplateVMs].
## Upgrading
Upgrading from your current release to a newer release.
There are two ways to upgrade a TemplateVM. The easiest way is to [install] the new Fedora TemplateVM next to the Fedora TemplateVM you are currently using. Then redo all desired template modifications, and switch everything that was set to the old template to the new template.To make this process as efficient as possible, document modifications to your TemplateVMs in a text file. If you do not have this documentation yet, open a terminal in the old Fedora TemplateVM, and use the `history` command. (There is currently no other way to gain a list of explicitly installed packages. Methods like `dnf repoquery --userinstalled` and `rpm -qa` all include packages that have been installed as dependencies.)
Please see [Upgrading Fedora TemplateVMs].
You can also do an in-place upgrade of an installed Fedora TemplateVM. Please see [Upgrading Fedora TemplateVMs].