updating archlinux gives this error:
installing pulseaudio (17.0+r43+g3e2bb8a1e-1) breaks dependency ‘pulseaudio<=17.0’ required by qubes-vm-pulseaudio
I don’t need audio in that qube so I tried the following which also failed. Any suggestions?
[root@archlinux ~]# sudo pacman -Rs pulseaudio
checking dependencies…
error: failed to prepare transaction (could not satisfy dependencies)
:: removing pulseaudio breaks dependency ‘pulse-native-provider’ required by gnome-settings-daemon
:: removing pulseaudio breaks dependency ‘pulseaudio<=17.0’ required by qubes-vm-pulseaudio
[root@archlinux ~]# sudo pacman -R qubes-vm-pulseaudio
checking dependencies…
error: failed to prepare transaction (could not satisfy dependencies)
:: removing qubes-vm-pulseaudio breaks dependency ‘qubes-vm-pulseaudio’ required by qubes-vm-dependencies
[root@archlinux ~]#
I successfully updated using:
sudo pacman -Syyu --ignore=pulseaudio,libpulse
Hopefully update manage updates will soon resume working without this work around.
So I read through all that, all the way to last week’s update and followed @marmarek’s link, but didn’t see anywhere where this was resolved, and I just experienced this issue a couple days ago. Like @InsideABoox I just --ignored it, but would still like a tangible update please.
The fix is currently in testing repository. Take a look at /etc/pacman.d directory within your Archlinux template. If you need the update earlier, you could change the symlink of 90-qubes-current.conf to 85-qubes-current-testing.conf.disabled to get the update right now. Or you could wait for some time for the patch to be moved to stable repo.
1 Like
Hi!
I have the same issue with Qubes 4.2. What I found is that the fixes PR247, PR250 were done for 4.3 but not backported to 4.2.
I can try to backport them to the 4.2 branch (there were some changes as the pulse stack changed in). Does someone know if the 4.2 branch is “on hold” or if I manage to make a patch it would be accepted?
Thanks!!
Hi.
One of those patches were merged just 3 days ago. And it takes time for them to be backported to the current stable branch (i.e. r4.2)
According to the official documentation:
Every new update is first uploaded to the security-testing repository if it is a security update or current-testing if it is a normal update. The update remains in security-testing or current-testing for a minimum of one week. On occasion, an exception is made for a particularly critical security update, which is immediately pushed to the current stable repository. In general, however, security updates remain in security-testing for two weeks before migrating to current. Normal updates generally remain in current-testing until they have been sufficiently tested by the community, which can last weeks or even months, depending on the amount of feedback received (see Providing feedback).
Thanks for the quick response!!
I forgot to say that I also tried the testing repo. What I am not sure is how are the branches handled as main points to 4.3 and probably as the new stable will be 4.3 in the near future.
In any case I understand that it is a incredible vast amount of work to maintain not only the official templates but also the unofficial templates and at the same time move things forward to 4.3. I am very very grateful all the work!
For the time being I am playing and trying to understand qubes-builderv2 that seems the way to rebuild the packages. Let’s see how far I can go.
Just for the record, I tried to hack around the Arch package and just change the dependency metadata. It did installed and was able to upgrade but then pulseaudio did not like the vchan module, so no sound. Hopefully I was able to rollback as I did it in a standard qube and not in the template.
EDIT: at the end the workaround of editing the package worked. I had to rebuild the vchan module. First updating libpulse and pulseaudio, then running make in this directory qubes-gui-agent-linux/pulse at main · QubesOS/qubes-gui-agent-linux · GitHub after creating a symlink of pulsecore-17.0 to pulsecore. So just editing the package metadata and building the module!