I’ve built Qubes packages and they are available at 3isec
Official packages will be available soon, but the build isn’t
yet straightforward so these are usable in the meantime.
The templates ship with the Qubes repository configured - you will need
to comment out the definition until those packages are built. If you
want to use the 3isec repo in the meantime, instructions for configuring that repository are given.
Resolute leans on snap, so I have included the qubes-snap-helper. If you
want firefox you will need to snap install firefox in your qube.
Due to a change in resolute’s sudo-implementation, you will get errors trying to run sudo. This can be fixed by commenting out everything in /etc/sudoers.d/qubes.
I did not use the Qubes repositories, because otherwise apt update threw an error. Maybe this is the reason why passwordless root did not work. So I had to set a password for the user user manually, because an empty password was not accepted by sudo.
Hi @unman, thanks to you for providing this template. I have installed it but when I attempt to update it I am seeing an error:
user@dom0:~$ qubes-vm-update --verbose --log DEBUG --force-update --targets resolute
resolute (error): 4%|████
resolute:out: Refreshing package info
resolute:out: Refreshing available packages.
resolute:err: Fail to refresh InRelease: https://debu.qubes-os.org/r4.3/vm resolute InRelease from https://debu.qubes-os.org/r4.3/vm/dists/resolute/InRelease
resolute:out: Refreshed.
resolute:err: Fail to refresh Release: https://debu.qubes-os.org/r4.3/vm resolute Release from https://debu.qubes-os.org/r4.3/vm/dists/resolute/Release
resolute:err: W:Repositories should provide a clear-signed InRelease file, but none found at https://debu.qubes-os.org/r4.3/vm/dists/resolute/InRelease., E:The repository 'https://debu.qubes-os.org/r4.3/vm resolute Release' does not have a Release file.
resolute:err: Hit:1 http://archive.ubuntu.com/ubuntu resolute-security InRelease
resolute:err: Hit:2 http://archive.ubuntu.com/ubuntu resolute-updates InRelease
resolute:err: Hit:3 http://fr.archive.ubuntu.com/ubuntu resolute InRelease
resolute:err: Ign:4 https://debu.qubes-os.org/r4.3/vm resolute InRelease
resolute:err: Err:5 https://debu.qubes-os.org/r4.3/vm resolute Release
resolute:err: 404 Not Found [IP: 127.0.0.1 8082]
resolute:err: Reading package lists...
resolute:err: E: The repository 'https://debu.qubes-os.org/r4.3/vm resolute Release' does not have a Release file.
Thank you. Unfortunately the result is much the same:
Updating resolute
Refreshing package info
Refreshing available packages.
Fail to refresh InRelease: https://deb.qubes-os.org/r4.3/vm resolute InRelease from https://deb.qubes-os.org/r4.3/vm/dists/resolute/InRelease
Refreshed.
Fail to refresh Release: https://deb.qubes-os.org/r4.3/vm resolute Release from https://deb.qubes-os.org/r4.3/vm/dists/resolute/Release
W:Repositories should provide a clear-signed InRelease file, but none found at https://deb.qubes-os.org/r4.3/vm/dists/resolute/InRelease., E:The repository 'https://deb.qubes-os.org/r4.3/vm resolute Release' does not have a Release file.
Hit:1 http://archive.ubuntu.com/ubuntu resolute-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu resolute-updates InRelease
Hit:3 http://fr.archive.ubuntu.com/ubuntu resolute InRelease
Ign:4 https://deb.qubes-os.org/r4.3/vm resolute InRelease
Err:5 https://deb.qubes-os.org/r4.3/vm resolute Release
404 Not Found [IP: 127.0.0.1 8082]
Reading package lists...
E: The repository 'https://deb.qubes-os.org/r4.3/vm resolute Release' does not have a Release file.
While writing this reply I note that the debu.qubes-os.org host appears to resolve. So perhaps it is not a mistake. I am unsure.
No. debu.qubes-os.org is correct. This is the repository for Ubuntu
packages. deb.qubes-os.org is the repository for Debian packages.
Resolute is a Ubuntu release.
The reason for the “not found” message is that official packages have
not yet been built for resolute.
You can comment out that repository for the moment, until official
packages have been released.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.