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 (python-mapnik) Fails To Install in Fedora 40: can't install python3-mapnik: - nothing provides libboost_thread.so.1.81.0()(64bit) needed by python3-mapnik-3.0.23-26.20200224git7da019c.fc39.x86_64 - nothing provides libboost_python312.so.1.81.0()(64bit) needed by python3-mapnik-3.0.23-26.20200224git7da019c.fc39.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 python3-mapnik 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!
*** This bug has been marked as a duplicate of bug 2259581 ***
For the record, if you close the bugs, the automation will open new ones until it actually is installable in the repository. I see you marked this as a duplicate of a *closed* bugzilla, but the problem persists (the fixed build is still not available). If you wish to not get bothered with new and new bugzillas, don't mark the original one CLOSED, but e.g. as RELEASE_PENDING or MODIFIED. I am sorry if this is annoying, but the automation really cannot read a comment by a human to figure out the fix is eventually landing for this.
Well I was expecting the mass rebuild to be merged back by now. Frankly I have no idea what's going on as it seems to be rebuilding the same things over and over again...
Seems it happened now: https://pagure.io/releng/issue/11888#comment-893699