Trying to update dom0, official testing repos enabled, enabled security-related testing updates only. Update goes through sys-whonix. Repo updates are download successfully, but the error goes like this:
problem with installed package qubes-desktop-linux-manager-4.2.17-1.fc37.noarch
nothing provides python3-qubesadmin >= 4.2-11 needed by qubes-desktop-linux-manager-4.2.20-1.fc37.noarch
There was this issue:
opened 05:25PM - 12 Jan 24 UTC
closed 02:03AM - 19 Feb 24 UTC
T: bug
C: manager/widget
P: major
security
diagnosed
pr submitted
C: updates
r4.2-vm-fc37-stable
r4.2-vm-bookworm-stable
r4.2-host-stable
r4.2-vm-fc38-stable
affects-4.2
r4.2-vm-fc39-stable
r4.2-vm-fc40-cur-test
r4.2-vm-trixie-stable
### Qubes OS release
4.2
### Brief summary
When choosing the "Enable … security-related testing updates only" option in the new Global Config app, section "Updates", almost no updates are actually received and packages, such as `qubes-repo-contrib` cannot be found.
If this is not intended behavior then it seems a pretty severe bug; when putting the selection back to "Enable stable updates only" and updating dom0, I received more than a dozen updates and was able to install `qubes-repo-contrib`. Therefore, my intention, which was to be ahead of the curve in keeping my system up to date with security-related updates while still receiving all updates for other packages, actually backfired and left my system behind with many packages, including ones that are presumably security related, such as `xen`, `xen-hypervisor`, `xen-libs`, `qubes-core-dom0`, `qubes-utils` etc...
After thinking about it more, this may be the intended behavior, as that option may be intended only for that one repo instead of what I thought, namely that it will install all stable packages and additionally security-related ones before they become stable, in which case I ask to change this issue to an enhancement request (the user should be told that this option should only be enabled temporarily for specific updates, not left as a permanent choice; alternatively, the behavior that I assumed and described above should be implemented).
### Steps to reproduce
1. Enable the option "Enable security-related testing updates only" option in the new Global Config app, section "Updates"
2. try to install e.g. `qubes-repo-contrib`
### Expected behavior
Enabling that option keeps access to stable repo open, but prefers packages in security-testing for those packages that are present in both repos.
### Actual behavior
Enabling that option breaks regular dom0 updates and ability to install common packages.
Enable stable updates in Qubes Global Config, update dom0 and after this enable security-related testing updates again.
1 Like