Dom0 update fail after inplace upgrade to 4.3.0--FIXED

[bengee]

Hello, I’m experiencing a dom0 update failure after an uneventful inplace upgrade from 4.2.4 to 4.3.0. This is through the gui. Everything else after the upgrade has been working great other than a minor annoyance with a pre-upgrade issue of having updated appVMs not restarting. If interested in that please see AppVMs not restarting after update but service VMs do.

However, regarding the dom0 update fail. All other VMs update just fine through the gui interface. The update proxy is sys-firewall for dom0 updates. I am not certain what the problem is but it seems maybe a remnant of fedora 37 is the issue. I did a dnf search for a kernel-qubes-vm-1000:6.12.63-1.qubes.fc41.x86_84 and also a 6.12.59 version for fc41 just to check another possibility but nothing was found. Is the update not using dnf in dom0? I thought it best to ask someone who might have experience in this area as I don’t want to poke around too much and remove something by mistake and break a good working system. I considered adding --skip-broken but dnf states nothing to do. Plus it doesn’t seem broken, just an incorrect existing file maybe? Thanks!

Problem: problem with installed package python3-qubesadmin-4.3.25-1.fc41.noarch

• cannot install the best update candidate for package python3-qubesadmin-4.3.25-1.fc41.noarch
• problem with installed package kernel-qubes-vm-1000:6.12.59-1.qubes.fc37.x86_64
• cannot install the best update candidate for package kernel-qubes-vm-1000:6.12.59-1.qubes.fc37.x86_64
• package kernel-qubes-vm-1000:6.12.59-1.qubes.fc41.x86_64 from qubes-dom0-current requires qubes-core-dom0, but none of the providers can be installed
• package kernel-qubes-vm-1000:6.12.63-1.qubes.fc41.x86_64 from qubes-dom0-current requires qubes-core-dom0, but none of the providers can be installed
  (the remaining updates then fail)

[scallyob]

Was about to post same problem. By going to Qubes Global Config and changing Updates setting to use “Enable all testing updates” instead of “Enable stable updates only” I was able to temporarily get around this problem.

[scallyob]

errors I got:

Fedora 41 - x86_64                              438 kB/s |  19 MB     00:44    
Fedora 41 - x86_64 - Updates                    470 kB/s | 8.4 MB     00:18    
Qubes Host Repository (updates)                  65 kB/s | 265 kB     00:04    
Error: 
 Problem: problem with installed package python3-qubesadmin-4.3.25-1.fc41.noarch
  - cannot install the best update candidate for package python3-qubesadmin-4.3.25-1.fc41.noarch
  - problem with installed package kernel-qubes-vm-1000:6.12.59-1.qubes.fc37.x86_64
  - cannot install the best update candidate for package kernel-qubes-vm-1000:6.12.59-1.qubes.fc37.x86_64
  - package kernel-qubes-vm-1000:6.12.59-1.qubes.fc41.x86_64 from qubes-dom0-current requires qubes-core-dom0, but none of the providers can be installed
  - package kernel-qubes-vm-1000:6.12.63-1.qubes.fc41.x86_64 from qubes-dom0-current requires qubes-core-dom0, but none of the providers can be installed
  - package kernel-qubes-vm-1000:6.12.64-1.qubes.fc41.x86_64 from qubes-dom0-current requires qubes-core-dom0, but none of the providers can be installed
  - package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.38-1.fc41.noarch from @System
  - package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.31-1.fc41.noarch from qubes-dom0-current
  - package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.34-1.fc41.noarch from qubes-dom0-current
  - package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.35-1.fc41.noarch from qubes-dom0-current
  - package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.36-1.fc41.noarch from qubes-dom0-current
  - package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.37-1.fc41.noarch from qubes-dom0-current
  - package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.38-1.fc41.noarch from qubes-dom0-current
(try to add '--skip-broken' to skip uninstallable packages)

[TheGardner]

Same here for me today… --skip-broken switch wouldn’t work also.

[taranis]

Same here, in place install:

Fedora 41 - x86_64 4.4 kB/s | 4.7 kB 00:01
Fedora 41 - x86_64 - Updates 5.0 kB/s | 4.6 kB 00:00
Qubes Host Repository (updates) 1.7 kB/s | 2.7 kB 00:01
Error:
Problem: problem with installed package python3-qubesadmin-4.3.25-1.fc41.noarch

• cannot install the best update candidate for package python3-qubesadmin-4.3.25-1.fc41.noarch
• problem with installed package kernel-qubes-vm-1000:6.12.59-1.qubes.fc41.x86_64
• cannot install the best update candidate for package kernel-qubes-vm-1000:6.12.59-1.qubes.fc41.x86_64
• package kernel-qubes-vm-1000:6.12.59-1.qubes.fc41.x86_64 from qubes-dom0-current requires qubes-core-dom0, but none of the providers can be installed
• package kernel-qubes-vm-1000:6.12.63-1.qubes.fc41.x86_64 from qubes-dom0-current requires qubes-core-dom0, but none of the providers can be installed
• package kernel-qubes-vm-1000:6.12.64-1.qubes.fc41.x86_64 from qubes-dom0-current requires qubes-core-dom0, but none of the providers can be installed
• package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.38-1.fc41.noarch from @System
• package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.31-1.fc41.noarch from qubes-dom0-current
• package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.34-1.fc41.noarch from qubes-dom0-current
• package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.35-1.fc41.noarch from qubes-dom0-current
• package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.36-1.fc41.noarch from qubes-dom0-current
• package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.37-1.fc41.noarch from qubes-dom0-current
• package python3-qubesadmin-4.3.27-1.fc41.noarch from qubes-dom0-current conflicts with qubes-core-dom0 < 4.3.39 provided by qubes-core-dom0-4.3.38-1.fc41.noarch from qubes-dom0-current
  (try to add ‘–skip-broken’ to skip uninstallable packages)

[ludovic]

See :

Dom0 update error, fresh Qubes 4.3 install

Looks like uploading core-admin-client v4.3.27 (r4.3) · Issue #6369 · QubesOS/updates-status · GitHub to the stable repository was premature… This needs matching core-admin v4.3.41 (r4.3) · Issue #6370 · QubesOS/updates-status · GitHub, but this one has still some issues, so it isn’t suitable for stable upload. The update issue should be fixed in few hours (after buggy package is removed from the stable repo).

[TheGardner]

@TheGardner

Same here for me today… --skip-broken switch wouldn’t work also.

…update successful…
was working for me now. At least the stop is fixed.
Thank you very much!

[bengee]

Hi Everybody, I just reran the update and the update code has been fixed for me and ran to completion successfully along with a couple other appVMs !! Thanks to whoever fixed the code!!

Thanks @TheGardner for the heads up!