there are no enabled repossitories in “/etc/yu.real.repos.d”
The independent vm cannot be updated. The netvm of the independent vm is none. I can update it after connecting to sys-whonix, but I don’t think this is the right approach at all. The purpose of the independent vm is that the data is more important, so it needs to be disconnected, right?
ping -c 4 yum.qubes-os.org reports Temporary failure in name resolution
ping -c 4 8.8.8.8 error, network unreachable
Why do I get so many errors? I kneel down and reinstall honestly by downloading the iso file. But I still want to understand why. Can anyone answer it? What went wrong? How to solve it?
I don’t intend animosity; but is “–enablerepo…” necessary? Qubes docs do not include that, just “sudo qubes-dom0-update -y qubes-dist-upgrade.” Not super important, but I think better to not enable the unnecessary repo in dom0.
Yes, could be a command from the “rc” days of 4.3, when qubes-dist-upgrade wasn’t available for the usual update/upgrade crowd and maybe it’s now available for all via
sudo qubes-dom0-update -y qubes-dist-upgrade
Not necessarily, he gave the option to skip it. If the independent VM must be connected to the Internet to upgrade, then why create an independent VM? For example: What is the encryption private key stored in your independent VM?
I upgraded by referring to the official documentation, but I still got a lot of errors. I don’t know if it was a problem with my environment or something else. Your command did not appear in the official documentation. In fact, if I don’t know much about the technology, I would prefer to strictly follow the official documentation. Unfortunately, there were still a lot of errors. In the end, I spent a day re-downloading and installing. It was so fucked.
yes, was very similar for me (in December) and the commands from the official documentation didn’t work that way and so I searched the forum here getting the command, which was grabbing the qubes-dist-upgrade function from the test repositories, so I got it installed and I was able to do the entire in-place-upgrade procedure after then.
But fact: if I’m a newly QubesOS user I always would follow (and prefer) not to do a in-place-upgrade, but a new and fresh install instead. And for the reason (not to destroy my old 4.2 system) I rather would buy a new device (if I have the money) or just buy a new SSD which I’ll use for the new 4.3 install to keep the old 4.2 SSD alive for a fall back.