Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ Your package (kwin-x11) Fails To Install in Fedora 40: can't install kwin-x11: - nothing provides libQt6Gui.so.6(Qt_6.7_PRIVATE_API)(64bit) needed by kwin-x11-6.2.5-1.fc40.x86_64 If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-40-x86_64 --config-opts mirrored=False install kwin-x11 P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
Rebuilding now.
128367798 build (f40-candidate, /rpms/kwin-x11.git:cce22748e03f25ccfad20007d6b1d3d2670aff96) completed successfully
FEDORA-2025-44c791d439 (kwin-x11-6.2.5-1.fc40.1) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-44c791d439
I would have done the rebuild myself (as for the other packages), but last time you reverted commits so I assumed you don't want me to do it anymore.
IIRC, I reverted the commits so I could sync the branches again when the new version was to be pushed. If I ever complained about a rebuild for dependencies (I do not remember whether I ever had to complain about one from you in particular or not), then it was because of the way Release was incremented (as you can see, I used the post-dist-increment (1.fc40.1) here because F41 is still at 1.fc41 and I do not want to break the upgrade path) or because of unnecessary changes to the specfile (such as using %auto… magic), surely not about the idea of a rebuild. And even if you want me to do the rebuild, dropping me a mail or preemptively filing a bug would have prevented the FTI.
FEDORA-2025-44c791d439 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-44c791d439` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-44c791d439 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
*** Bug 2342639 has been marked as a duplicate of this bug. ***
Please, instead of filing duplicates (or just CCing yourselves here), give the update: https://bodhi.fedoraproject.org/updates/FEDORA-2025-44c791d439 a +1 in Bodhi so it can go to stable. (It needs +2 (critical path update), it has +1.)
*** Bug 2343683 has been marked as a duplicate of this bug. ***
Folks, https://bodhi.fedoraproject.org/updates/FEDORA-2025-44c791d439 still needs an additional +1 vote or it is stuck for 3 more days. Nothing I can do about it, we are not allowed to vote on our own updates. (Bodhi will just ignore the maintainer's vote.)
On the other hand, ANY user with a FAS account (except the submitter (me) or those who have already voted +1) can give the missing +1 vote.
FEDORA-2025-44c791d439 (kwin-x11-6.2.5-1.fc40.1) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
(In reply to Jan Grulich from comment #4) > I would have done the rebuild myself (as for the other packages), but last > time you reverted commits so I assumed you don't want me to do it anymore. As you can see, I have now also reverted my own rebuild commit as part of the 6.3.0 merge. That is an integral part of the process I use to resynchronize the branches and not any sort of indication that there is anything wrong with the rebuild.