Fixing existing CI/CD issues

This commit is contained in:
Ali Mirjamali 2025-05-18 21:42:07 +03:30
parent b594557061
commit 2b028834a6
No known key found for this signature in database
GPG key ID: B4A5C188DF4FAB67
4 changed files with 6 additions and 7 deletions

View file

@ -164,8 +164,8 @@ Please see [How to Update](/doc/how-to-update/).
## Why don't templates have normal network access?
In order to protect you from performing risky activities in templates, they do
not have normal network access by default. Instead, templates use an [updates
proxy](#updates-proxy) which allows you to install and update software using
not have normal network access by default. Instead, templates use an
[updates-proxy](#updates-proxy)which allows you to install and update software using
the distribution's package manager over the proxy connection.
**The updates proxy is already set up to work automatically out-of-the-box and
requires no special action from you.**

View file

@ -158,7 +158,7 @@ As of Qubes 4.2, firmware updates can be performed from within Qubes for [fwupd-
### In dom0
First, ensure that your [UpdateVM](/doc/Software/UpdateVM/)
First, ensure that your UpdateVM
contains the `fwupd-qubes-vm` package. This package is installed
by default for qubes with `qubes-vm-recommended` packages.
@ -198,8 +198,7 @@ Repeat the update process for any additional devices on your computer.
Devices that are attached to non-dom0 qubes can be updated via a graphical tool for `fwupd`, or via the `fwupdmgr` commandline tool.
To update the firmware of offline qubes, use the [Updates
proxy](/doc/how-to/install/software/#updates-proxy).
To update the firmware of offline qubes, use the [Updates proxy](/doc/how-to-install-software/#updates-proxy).
### Computers without fwupd support