Thank you so much for your answers, @unman !
Things are much clearer to me now!
-
OK, I will try that
-
I thought that method worked only for text file. Thanks for the tip!
-
Great explanation! Great feeling to understand what’s going on and… Why!
-
Explained under 3 ==> OK
-
&6. So if I understand correctly, I should go in my kali template and type:
-
To update every packages in the template without touching Qubes packages:
-
sudo apt-mark hold qubes-*
NB: I get (among many other lines):
qubes-core-agent set on hold.
Or would have
sudo apt-mark hold qubes-core-*
been sufficient? -
sudo apt update && sudo apt upgrade
I am applying those commands to a kali template I had made by myself (which might be “broken” as a consequence of what you explained in 3) and I get as as result (among many other lines):
Processing triggers for qubes-core-agent (4.0.61-1+deb11u1) ...
Is it normal that I see this line? I mean
qubes-core-agent
was supposed to be set on hold, so how can triggers for a package on hold be processed?
-
-
Then to upgrade the
qubes-*
packages:-
sudo apt-mark unhold qubes-*
-
sudo apt-mark showhold
Noting appears ==> Fine!
-
sudo apt update && sudo apt upgrade
I guess the
sudo apt update
is not really necessary here since apt was anyway updated just before.NB: Only
qubes-usb-proxy
needs to be upgraded in my present case ==> Fine
-
-
Prepare for the next update && upggrade a.k.a. restoring the hold:
sudo apt-mark hold qubes-*
-
It is exactly the kind of explanations I was looking for!! The feeling of understanding is great!!
I can confirm this! It was due to a lack of knowledge, though. So great to know it won’t happen anymore!!!
Could you check my last questions here above to be sure I fully understand the details? Hopefully, this will be a great resource on the forum too because I’m pretty sure I was not the only guy not understanding what is happening!
Many thanks again, @unman!!