My initial reply got lost in transition.
Hi,
I would have some questions on the template page: https://qubes.3isec.org/Templates .
in dom0 sudo dnf install qubes-template-kali-4.0.6-202106091045.noarch.rpm
You can copy the file in to dom0: this is covered in the docs
Templates like Parrot or Kali are based on Debian testing. To avoid breakage when updating the core Qubes packages are on hold.
Debian testing is, as the name suggests, a testing distribution.
Packages change, and are updated rapidly. If the Qubes packages have
certain dependencies, then the updated packages in Debian or Kali may
break the Qubes packages, and the Qubes packages may be removed. (This
is the source of much confusion and pain for people who don’t check to
see what the package manager will be doing.)
This doesn’t happen in standard versions of Debian, because the package
transitions there are much slower, and the Qubes packages tested against
them.
The same situation can arise in any rolling distribution like Arch.
‘apt-mark unhold’ will remove the hold and allow you to update the Qubes packages.
Does this make it clearer?
To avoid breakage when updating, the core Qubes packages are on hold.
The process is a little complicated.
When the hold is activated, you just run apt update
and apt upgrade
as usual. The hold will prevent the Qubes packages from being removed,
so some of the Debian or Kali packages will be held back.
You can update a single package by using apt install <package>
. Or you
can use a package manager like aptitude, which will allow you to
select the packages to be updated.
Exactly so.
That’s fine: I hope this is readable.
You could have found the answers to some of this on the Qubes
documentation.
For many commands, man <command>
will provide useful information. In
this case man apt-mark
will explain about the use of hold and unhold,
as well as other marks you can set.