First of all, thank you for posting the Fedora 43 announcement and all the work done by the core team, testers, and larger community.
I’m trying to do an in-place upgrade of some fedora-42-minimal templates. The fedora-42 versions of these templates have been normally updating without any issues. When I enter dnf --releasever=43 --best distro-sync --allowerasing, I am getting the following error.
Problem: problem with installed package
- cannot install the best update candidate for package python3-gbulb-0.6.5-2.fc42.noarch
- python3-gbulb-0.6.5-2.fc42.noarch does not belong to a distupgrade repository
- nothing provides (python3.14dist(pygobject) < 3.50~~ with python3.14dist(pygobject) >= 3.14) needed by python3-gbulb-0.6.6-1.fc43.x86_64 from qubes-vm-r4.3-current
You can try to add to command line:
--no-best to not limit the transaction to the best candidates
--skip-broken to skip uninstallable packages
If I use the --no-best option, the template will get updated to 43. However, when I run the Qubes Update manager, I’m now getting this message.
Updating fedora-43-minimal-customized
Refreshing package info
Removed 0 files, 0 directories (total of 0 B). 0 errors occurred.
Problem: cannot install the best update candidate for package python3-gbulb-0.6.5-7.fc43.noarch
- nothing provides (python3.14dist(pygobject) < 3.50~~ with python3.14dist(pygobject) >= 3.14) needed by python3-gbulb-0.6.6-1.fc43.x86_64 from qubes-vm-r4.3-current
Installed packages:
None
Updated packages:
None
Removed packages:
None
A few questions:
-
Will this issue get fixed in a reasonable timeframe?
-
If I update templates now using the
--no-bestoption, will it create problems later when the issue is resolved? I have a large number of minimal templates (without SALT scripts), and I want to avoid re-work. I am not using the “pseudo-converted” templates. am not using the “pseudo-converted” templates. -
Or is the best course of action to simply wait a few days/weeks? While I’m not in a big rush, I always want to stay on the latest Fedora (and Debian) templates for EOL and other reasons.
-
Has anyone else had this issue? My customizations aren’t extensive, but one never knows if something is now causing an issue. However, I’ve seen the same error in two different templates, both originally based on official fedora-minimal templates. I’ve done several in-place updates of these templates (e.g., 40 → 41, etc.) without any problems.
Any guidance/comments would be appreciated. Thanks in advance.