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 (espresso) Fails To Install in Fedora 40: can't install python3-espresso-mpich: - nothing provides libboost_filesystem.so.1.81.0()(64bit) needed by python3-espresso-mpich-4.2.1-5.fc39.x86_64 - nothing provides libboost_serialization.so.1.81.0()(64bit) needed by python3-espresso-mpich-4.2.1-5.fc39.x86_64 - nothing provides libboost_mpi.so.1.81.0()(64bit)(mpich-x86_64) needed by python3-espresso-mpich-4.2.1-5.fc39.x86_64 can't install python3-espresso-openmpi: - nothing provides libboost_filesystem.so.1.81.0()(64bit) needed by python3-espresso-openmpi-4.2.1-5.fc39.x86_64 - nothing provides libboost_serialization.so.1.81.0()(64bit) needed by python3-espresso-openmpi-4.2.1-5.fc39.x86_64 - nothing provides libboost_mpi.so.1.81.0()(64bit)(openmpi-x86_64) needed by python3-espresso-openmpi-4.2.1-5.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-espresso-mpich python3-espresso-openmpi 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!
The package couldn't be rebuilt to use the new boost because of test failures during the rpm build: The following tests FAILED: 31 - constraint_shape_based (Failed) 37 - dawaanr-and-dds-gpu (Failed) 38 - dawaanr-and-bh-gpu (Failed) 39 - dds-and-bh-gpu (Failed) 58 - scafacos_dipoles_1d_2d (Failed) 59 - scafacos_interface (Failed) 81 - ek_fluctuations (Failed) 82 - ek_charged_plate (Failed) 83 - ek_eof_one_species_x (Failed) 84 - ek_eof_one_species_y (Failed) 85 - ek_eof_one_species_z (Failed) 96 - virtual_sites_tracers_gpu (Failed) 113 - lb_vtk (Failed) 146 - lb_electrohydrodynamics (Failed) 150 - drude (Failed) 153 - thole (Failed) 187 - stokesian_dynamics (Failed) 188 - stokesian_thermostat (Failed) 193 - h5md (Timeout) 195 - mdanalysis (Failed) Errors while running CTest
There are several inter-independent issues at play. 1) In Python 3.12, module unittest now returns exit code 5 when all tests are skipped. This is interpreted as a failure by CTest, which explains why the testsuite fails without producing any error message. This is something I will fix ASAP. The solution is to add `set_tests_properties(${TEST_NAME} PROPERTIES SKIP_RETURN_CODE 5)` to the CMake code that sets up the testsuite. For more details, see https://github.com/python/cpython/issues/106584 and https://cmake.org/cmake/help/latest/prop_test/SKIP_RETURN_CODE.html 2) In one test, we rely on a deprecated feature removed from Python 3.12. I will fix that ASAP. 3) When running the testsuite inside a Docker image on an x86_64 machine, I get the following error message: ``` 6/201 Test #84: ek_eof_one_species_y ..........................................***Failed 1.97 sec [6d78815295c7:07847] PMIX ERROR: PMIX_ERROR in file client/pmix_client_topology.c at line 352 [6d78815295c7:07847] PMIX ERROR: PMIX_ERROR in file client/pmix_client_topology.c at line 352 ss ---------------------------------------------------------------------- Ran 0 tests in 0.000s NO TESTS RAN (skipped=2) ``` The actual issue is that unittest returns exit code 5 and will be fixed by the solution outline in point 1). The PMIX error is actually just a warning. This is a known issue with OpenMPI 5.0.1 and PMIX 2.9.3, see the bug report here: https://github.com/open-mpi/ompi/issues/12146
All issues were addressed in release espresso-4.2.1-10.fc40, submitted for stable by Bohdi: https://bodhi.fedoraproject.org/updates/FEDORA-2024-2383d4efbb
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/ All subpackages of a package against which this bug was filled are now installable or removed from Fedora 40. Thanks for taking care of it!
FEDORA-2024-2bd1377acc has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-2bd1377acc
FEDORA-2024-2bd1377acc has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-2bd1377acc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-2bd1377acc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-2bd1377acc (espresso-4.2.1-8.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.