Set those packages in /etc/pacman.conf to ignore because there are qubes-* packages which conflict with newer versions:
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg = python
IgnorePkg = xorg-server
IgnorePkg = pulseaudio libpulse
Looks like arch users have to wait until the qubes-* packages catch up.
Start your arch-template and edit /etc/pacman.conf as shown above. Shutdown the arch-template and try the Qubes Updater for your arch-template again. Packages should update/upgrade but you’ll get an error message nonetheless. A different one, though.
The builder builds the last commit of each packages, the current repository contains the last stable released packages.
I think this is not implemented for Arch. Arch isn’t an officially supported template. But from my point of view, the update notification is useless for Arch, because each day I see an update with a minimum of 3-4 packages…
Note that the update command from the Qubes manager works (right-click on the template, Update).
Arch is a rolling distribution, it is one of the first distribution to include the new versions. So yes, you should wait the qubes-* packages, or best you do the changes and do a PR to the related Qubes-OS github repositories. Since june 22th, qubes-vm-pulseaudio is compatible with pulseaudio 16.x.
archlinux# pacman -Syu
:: Synchronizing package databases...
qubes-r4.1.db failed to download
error: failed retrieving file 'qubes-r4.1.db' from archlinux.qubes-os.org : The requested URL returned error: 404
error: failed to synchronize all databases (failed to retrieve some files)
Turns out the database is named qubes-r4.1-current.db, therefore
archlinux# cat 99-qubes-repository-4.0.conf
[qubes-r4.1-current]
Server = https://archlinux.qubes-os.org/r4.1/current/vm/archlinux/pkgs
call the repo qubes-r4.1-current instead of qubes-r4.1.
(11/13) Updating the Qubes desktop file App Icons and features...
Request refused
Traceback (most recent call last):
File "/usr/bin/qvm-features-request", line 30, in <module>
import qubesdb
ModuleNotFoundError: No module named 'qubesdb'
For the same reason that in Kali template Qubes Packages are on hold. I’m new to arch and don’t know if there will be upgrade with conflicted dependencies pacman can delete Qubes Packages.
In case of conflicts pacman should stop the update/upgrade-process. Putting packages at hold can work for a while, but ultimately this will lead to more packages not being able to be updated. Sorry for mixing another topic into your thread.
Anyway, upgrades-status-notify and upgrades-installed-check are bash-scripts. I inspected them in a fedora-36-VM and qvm-copy-ied them into my arch-template.
Now the Qubes Updater works for my archlinux-template without error.
But don’t do this kind of stuff at home. That’s a recipe for desaster. Or at least have a look at the scripts to get a sense of what they are doing.
My Qubes OS has been freshly installed as v4.1 at the beginning of this year. Afterwards I restored the arch template and appVM from a backup.
Have you migrated from v4.0 to v4.1, too? Newer templates might get delivered with upgrades-status-notify and upgrades-installed-check in place (/usr/lib/qubes/).
@ludovic: does your arch template contain these scripts?
No, I install my Qubes as 4.1 and build arch using qubes-builder last week - so as we agreed is the reason why I have newer packages than that on repo. But I also try using arch few months ago, and it also don’t have that scripts.
I saw that lack of confirmation of update for arch was mentioned in some issue from last year but this issue was closed and fix should be merged. Maybe it wasn’t merged.