Qubes installs packages from wrong repo

User Support
1

Hello,

I installed Qubes 4.3 when it was in the release candidate stage and switched from qubes-testing to stable shortly after it became stable.

In the Qubes OS Global Config menu, I only have “Enable stable updates only” enabled. However, Qubes is still installing packages from the testing repository:

Dependencies resolved.
=================================================================================================================
 Package                                  Arch    Version                       Repository                   Size
=================================================================================================================
Upgrading:
 microcode_ctl                            x86_64  3:2.1.20260210-58.qubes1.fc41 qubes-dom0-current-testing   13 M
 python3-gbulb                            x86_64  0.6.6-2.fc41                  qubes-dom0-current-testing   57 k
 qubes-core-dom0                          noarch  4.3.42-1.fc41                 qubes-dom0-current          1.3 M
 qubes-core-dom0-linux                    x86_64  4.3.21-1.fc41                 qubes-dom0-current          157 k
 qubes-core-dom0-linux-kernel-install     x86_64  4.3.21-1.fc41                 qubes-dom0-current           15 k
 qubes-manager                            noarch  4.3.21-1.fc41                 qubes-dom0-current-testing  391 k
 qubes-usb-proxy-dom0                     noarch  4.3.4-1.fc41                  qubes-dom0-current-testing   58 k
 scrypt                                   x86_64  1.3.3-1.fc41                  qubes-dom0-current-testing   43 k

Additionally, in the Qubes OS Global Config, I see a error message: “Error accessing repository data. Cannot change update settings. Encountered error: qrexec call failed: none.”

In the dom0 log, I have this error message:

Feb 11 21:44:45 dom0 qubes-app-menu[21110]: Traceback (most recent call last):
Feb 11 21:44:45 dom0 qubes-app-menu[21110]:   File "/etc/qubes-rpc/qubes.repos.List", line 6, in <module>
Feb 11 21:44:45 dom0 qubes-app-menu[21110]:     import dnf
Feb 11 21:44:45 dom0 qubes-app-menu[21110]: ModuleNotFoundError: No module named 'dnf'

What can i do to disable the testing repo?

2

I always work with testing enabled for reasons, and I dont see this
behavior. Disabling the testing repositories works fine, with no error
message. So I suspect if there was an issue it has been resolved in the
latest packages.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

1 Like
3

After installing the most recent update and rebooting the issue is not resolved on my computer.

I suppose this issue ocured because I removed qubes-mgmt-salt from dom0 to reduce the attack surface and amount of packages. I guess the dependency to python-dnf is not correctly specified in the packages for the Qubes OS Global Config.