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-best option, 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.
Yes, assume the update candidate will be available later, although someone (else) may need to create an issue on the GitHub repository if it does not exist already.
Thanks @FranklyFlawless. I did a quick search for python3-gblub on the Qubes Issues Github. I also manually scan through open issues since the start of 2026. Unless I missed something, I didn’t see any issues opened directly related to this problem.
However, on issue Fedora 43 template #10102, @alimirjamalimentioned back in Aug. 2025 that this package is no longer in the Fedora 43 repo, and it should be removed accordingly. I’m not sure if this comment was related to its removal or not. Regardless, as of now, this package is back in the Fedora 43 repo, as well as Fedora 44 and Rawhide.
Hi @alimirjamali - Thank you for all that you do to support the Qubes project, including the Qubes OS Update Weekly Reviews. To be clear, I’m not saying that you caused this issue, since the package was apparently missing from the repo last August. I’m just interested in getting the issue resolved in the next few days/weeks. Per my comments above, I’m happy to open an issue in Github, or should I comment on the “somewhat-related” thread on #10102? Please let me know. Thanks again.
<Edit: I will just add a comment to the #10102 issue on Github>
I tagged you because you’ve been actively contributing to the Qubes documentation on the github repository lately. However, it turned out that there was nothing to do.
Yes, to include the removal step in the documentation, although it’s not necessary at the moment. Since you’ve been updating the documentation, I thought you would add this as well, but you seem confused for some reason.
Yes: I would be glad to help anyone who want to update the docs, but it turns out you mentioned me to get me to do something. So, I just want to be clear that IMO it’s inappropriate. Nobody tells me what I should do, especially when you could do it yourself.
How is anything I said inappropriate? I tagged you because you’ve been updating the documentation and have several open/merged pull requests on the repository. I also don’t understand how my message was an order for you to do something. It was more of a suggestion. If you don’t want to do it, that’s fine. But, once again, I tagged you because you have been managing the documentation much more than anyone else recently. Since the documentation is a community effort and some people have more access than others, I suggested you add it. For what it’s worth, I don’t have a GitHub account, so I can’t contribute.
I value mutual assistance rather than delegating tasks to someone else. That’s why I used “IMO,” to let you know how I feel about this. I understand that this value might be very personal, and my message may have been poorly written because it has nothing to do with what is “(in)appropriate” on the forum. It is just about me.
You don’t have to use a Github account to submit a patch. Usually, I don’t use it but if you had sent it, I would have been happy to try to make a PR based on it.
Also, I’m not managing anything and I don’t have “more access”. If you could elaborate on how I give that impression, it would help me fix it.