Has anybody tried doing the in place upgrade from 4.1 to 4.2?
This article contains the instructions, but when the following step is run:
sudo qubes-dist-upgrade --all-pre-reboot
“STAGE 1” seems to fail at least on the debian-12 template:
debian-12: ERROR (exit code 20, details in /var/log/qubes/mgmt-debian-12.log)
after the templates upgrade(except for debian-12), the script will not progress past
STAGE 1.
Check the error details in /var/log/qubes/mgmt-debian-12.log.
various error message s are present:
Failed to fetch tor-http://deb…
Some index files failed to download.They have been ignored, or old ones used
instead.
Maybe it was a transient issue with network connection. Did you try to run the sudo qubes-dist-upgrade --all-pre-reboot again so that debian-12 template will update successfully?
It’s been attempted more than once, yes.
Change the updatevm used by this script to sys-whonix since you’re using onion repos:
--updatevm, -f Current UpdateVM defined (default 'sys-firewall').
The dom0 update qube has been changed to sys-whonix.
The attempted command was:
sudo qubes-dist-upgrade --all-pre-reboot --updatevm -f sys-whonix
debian-12: ERRROR
The connection error mentioned above still persists. This is even after changing
to an obfs4 bridge, or to no bridge, or meek-azure.
The same “Failed to fetch” for the .onion repo for the r4.1 Qubes version.
Can you try accessing the repos using Tor Browser in Whonix Workstation qube through sys-whonix?
Just to make sure that Tor and repos are working fine.
http://deb.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/r4.1/vm/dists/bookworm/
This link loads fine using the Tor Browser.
I’m not sure how it works, but you need to use either --updatevm or short -f flag, not both of them:
sudo qubes-dist-upgrade --all-pre-reboot --updatevm sys-whonix
or
sudo qubes-dist-upgrade --all-pre-reboot -f sys-whonix
I had previously attempted using --updatevm just on its own without “-f” for example.
Can you post the full log for debian-12?
E: The method driver /usr/lib/apt/methods/tor+http could not be found.
W: http://repos.azulsystems.com/debian/dists/stable/Release.gpg: Key is stored
in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section
in apt-key(8) for details.
Remove all tor+ from the repository files in debian-12.
sudo sed -i "s|tor+||g" /etc/apt/sources.list /etc/apt/sources.list.d/*
which directory is that again? /etc/conf.d?
I can see you’ve edited your original post to include a helpful command.
what does “tor+” prefix actually do to this URL?
It’s telling the package manager to use apt-transport-tor:
E: The method driver /usr/lib/apt/methods/tor+http could not be found
Is this statement referring to apt-transport-tor being missing? Is the package
missing?
Yes, the package is missing, but just installing the package won’t work, you need to configure it to use sys-whonix as well since apt-transport-tor assuming that tor process is running in the system.