Dear maintainer: During a rebuild of all packages in unstable, this package failed to build. Below you will find the last part of the build log (probably the most relevant part, but not necessarily). If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202608/ About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages. If you cannot reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and add an affects on src:cp2k, so that this is still visible in the BTS web page for this package. Thanks. -------------------------------------------------------------------------------- [...] Resolving dependencies for psmp ... /<<PKGBUILDDIR>>/tools/build_utils/makedep.py /<<PKGBUILDDIR [too-long-redacted] PKGBUILDDIR>>/src/ace_c_api.cpp /<<PKGBUILDDIR>>/Makefile:147: update target 'all' due to: target is .PHONY /usr/bin/make --no-print-directory -C /<<PKGBUILDDIR>>/obj/Linux-x86_64-gfortran/psmp -f /<<PKGBUILDDIR>>/Makefile all INCLUDE_DEPS=true /<<PKGBUILDDIR>>/Makefile:515: update target 'kinds.o' due to: target does not exist /<<PKGBUILDDIR>>/tools/build_utils/fypp -n /<<PKGBUILDDIR>>/src/base/kinds.F kinds.F90 mpif90 -c -g -Wall -O2 -fopenmp -funroll-loops -ftree-vectorize -ffree-form -ffree-line-length-none -fallow-argument-mismatch -D__GFORTRAN -D__FFTSG -D__FFTW3 -D__LIBINT -D__LIBXC -D__SPGLIB -D__parallel -D__BLACS -D__SCALAPACK -D__ELPA=202111 -I/usr/include/elpa/modules/ -I/usr/include/elpa/elpa/ -I/usr/include -D__COMPILE_ARCH="\"Linux-x86_64-gfortran\"" -D__COMPILE_DATE="\"Thu Aug 6 09:10:20 UTC 2026\"" -D__COMPILE_HOST="\"sbuild\"" -D__COMPILE_REVISION="\"git:3158929\"" -D__DATA_DIR="\"/usr/share/cp2k\"" -D__SHORT_FILE__="\"base/kinds.F\"" -I'/<<PKGBUILDDIR>>/src/base/' kinds.F90 -------------------------------------------------------------------------- The Open MPI wrapper compiler was unable to find the specified compiler gfortran-15 in your PATH. Note that this compiler was either specified at configure time or in one of several possible environment variables. -------------------------------------------------------------------------- make[5]: *** [/<<PKGBUILDDIR>>/Makefile:516: kinds.o] Error 1 make[4]: *** [/<<PKGBUILDDIR>>/Makefile:147: all] Error 2 make[3]: *** [/<<PKGBUILDDIR>>/Makefile:129: psmp] Error 2 make[2]: *** [Makefile:124: all] Error 2 make[2]: Leaving directory '/<<PKGBUILDDIR>>' make[1]: *** [debian/rules:70: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:56: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2 --------------------------------------------------------------------------------
Hi, I don't see that when I try to rebuild cp2k, I think it was a transient issue, can you try again? Michael
You are right that the precise error which I reported does no longer happen. I was indeed able to rebuild the package without errors on 2026-08-10 but yesterday it started to fail again, now in this way:------------------------------------------------------------------ ******************************************************************************* * ___ * * / \ * * [ABORT] * * \___/ MPI error 5 in mpi_comm_rank @ mp_comm_size : MPI_ERR_COMM: * * | invalid communicator * * O/| * * /| | * * / \ mpiwrap/message_passing.F:1305 * ******************************************************************************* ===== Routine Calling Stack ===== 8 mp_comm_size 7 arnoldi_extremal 6 qs_ot_get_p 5 ot_scf_init 4 init_scf_loop 3 scf_env_do_scf 2 qs_energies 1 CP2K -------------------------------------------------------------------------- MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD Proc: [[23235,1],0] Errorcode: 1 NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes. You may or may not see output from other processes, depending on exactly when Open MPI kills them.------------------------------------------------------------------ For reference, I've put my last failed build log (made yesterday) in the same directory as before: https://people.debian.org/~sanvila/build-logs/202608/ Can we retitle the bug, or do you prefer to close it so that I report a brand new one? (I've started yet another rebuild today to be sure). Thanks.
close 1143794 thanks Actually, to avoid confusion, I believe it's better to close the old bug, so I'm doing that myself. Thanks.
Hi. I'm not reporting this yet, but you might want to take a look: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cp2k.html (This is more or less the same error I got yesterday) Thanks.
Hi, Yeah, that's what I've been seeing all weekend as well trying to build the new upstream releases 2026.1 and 2026.2 in experimental. I now tried with the old unstable version and hit it there as well (after it went through the configure stage fine). Interesting that it only started to fail yesterday, I'll try with an earlier openmpi version then. Michael
necessarily when it actually started to fail (so I expressed it poorly, sorry). This is my build history: Status: successful cp2k_2025.2-3_amd64-20260810T155131.511Z Status: successful cp2k_2025.2-3_amd64-20260810T155219.633Z Status: failed cp2k_2025.2-3_amd64-20260822T111909.499Z Status: failed cp2k_2025.2-3_amd64-20260822T145012.811Z Status: failed cp2k_2025.2-3_amd64-20260823T154806.629Z Status: failed cp2k_2025.2-3_amd64-20260823T154806.528Z Status: failed cp2k_2025.2-3_amd64-20260823T154903.834Z Status: failed cp2k_2025.2-3_amd64-20260823T154905.454Z (No history before that because I usually remove old failed logs after a successful build). In theory, it would be possible to use debbisect to determine the exact point where it started to fail, but I did not try because the package has a long build time. Thanks.