I haven’t been able to update dom0 for some time. Using the “Qubes Update” GUI I get this message:
Updating dom0
Error on updating dom0: Command '['sudo', 'qubesctl', '--dom0-only', '--no-color', 'pkg.upgrade', 'refresh=True']' returned non-zero exit status 1.
[ERROR ] Command 'systemd-run' failed with return code: 1
[ERROR ] stderr: Running scope as unit: run-rda8a1dc0dd9146408f39d75e622d57ca.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--clean' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 1
[ERROR ] retcode: 1
Error running 'pkg.upgrade': Problem encountered upgrading packages. Additional info follows:
changes:
----------
result:
----------
pid:
49179
retcode:
1
stderr:
Running scope as unit: run-rda8a1dc0dd9146408f39d75e622d57ca.scope
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time...
Running '/usr/lib/qubes/qubes-download-dom0-updates.sh --doit --nogui '--exclude=qubes-template-*' '--quiet' '-y' '--clean' '--action=upgrade'' on sys-firewall
sys-firewall: command failed with code: 1
stdout:
If I run sudo qubes-dom0-update in a dom0-terminal I see the following in the opened sys-firewall terminal:
Qubes Dom0 Repository (updates) 11 kB/s | 2.7 kB 00:00
Error:
Problem: problem with installed package kernel-qubes-vm-1000:5.15.81-1.fc32.qubes.x86_64
- cannot install the best update candidate for package kernel-qubes-vm-1000:5.15.81-1.fc32.qubes.x86_64
- package kernel-qubes-vm-1000:5.15.94-1.qubes.fc32.x86_64 requires qubes-prepare-vm-kernel >= 2, but none of the providers can be installed
- nothing provides busybox needed by qubes-kernel-vm-support-4.1.19-1.fc32.x86_64
(try to add '--skip-broken' to skip uninstallable packages)
Fetching updates failed with code 1; press Enter to exit
Any suggestion on how to resolve this would be most welcome.
This is strange because I was able to install this version without
incident.
That’s wrong, and suggests there is something wrong with your
configuration.
Can you check your repository definitions under /etc/yum.repos.d/qubes-dom0.repo
What template are you using for sys-firewall.
Thanks for helping me track down the problem. The template used by sys-firewall is fedora-36, and the content of /etc/yum.repos.d/qubes-dom0.repo follows:
Those repository definitions look fine - notice that only the
“current” Qubes repository is enabled. (enabled = 1)
busybox is provided in the main fedora repository - the fact that you see
“nothing provides busybox” suggests that there’s something amiss with
that definition.
Look at the repo definition in fedora.repo and fedora-updates.repo- you should see that the stanza headed "[fedora]" hasenabled=1infedora.repo`
Can you check that?
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.
I checked fedora.repo and fedora-updates.repo. Nothing was enabled, so I enabled [fedora] in fedora.repo . Now I get a different error:
Error:
Problem: cannot install the best update candidate for package elfutils-libelf-0.183-1.fc32.x86_64
- cannot install both elfutils-libelf-0.179-1.fc32.x86_64 and elfutils-libelf-0.183-1.fc32.x86_64
- package elfutils-libelf-devel-0.179-1.fc32.x86_64 requires elfutils-libelf(x86-64) = 0.179-1.fc32, but none of the providers can be installed
- elfutils-libelf-devel-0.179-1.fc32.i686 has inferior architecture
- package kernel-devel-1000:5.15.94-1.qubes.fc32.x86_64 requires elfutils-libelf-devel, but none of the providers can be installed
- package kernel-qubes-vm-1000:5.15.94-1.qubes.fc32.x86_64 requires kernel-devel = 5.15.94-1.qubes.fc32.x86_64, but none of the providers can be installed
- problem with installed package kernel-qubes-vm-1000:5.15.81-1.fc32.qubes.x86_64
- cannot install the best update candidate for package kernel-qubes-vm-1000:5.15.81-1.fc32.qubes.x86_64
(try to add '--skip-broken' to skip uninstallable packages)
Should I set enabled=1 under [updates] in fedora-updates.repo as well?