Your message dated Sat, 16 Apr 2022 13:32:55 +0200
with message-id <5e985d0a6b43dded0dd5e6c23bdd3...@debian.org>
and subject line Re: Bug#1002082 mpi4py: FTBFS: testJoin socket.gaierror: Name
or service not known
has caused the Debian Bug report #1002082,
regarding mpi4py: FTBFS: testJoin socket.gaierror: Name or service not known
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1002082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpi4py
Version: 3.1.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_build override_dh_auto_build-arch -- \
> --build-args "--mpicc=/usr/bin/mpicc --mpicxx=/usr/bin/mpicxx"
> I: pybuild base:237: /usr/bin/python3.10 setup.py build
> --mpicc=/usr/bin/mpicc --mpicxx=/usr/bin/mpicxx
> running build
> running build_src
> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/__init__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/__main__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/run.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/bench.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/__init__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/aplus.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/__main__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/_lib.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/pool.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/server.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/_base.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/_core.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/util
> copying src/mpi4py/util/__init__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/util
> copying src/mpi4py/util/pkl5.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/util
> copying src/mpi4py/util/dtlib.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/util
> copying src/mpi4py/py.typed ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/run.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/bench.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/__main__.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/MPI.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/__init__.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/dl.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/__init__.pxd ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/MPI.pxd ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> copying src/mpi4py/libmpi.pxd ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/include
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi4py.MPI.h ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi4py.h ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi4py.MPI_api.h ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi4py.i ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/include/mpi4py
> copying src/mpi4py/include/mpi4py/mpi.pxi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/include/mpi4py
> copying src/mpi4py/futures/pool.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/_lib.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/_core.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/aplus.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/__main__.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/__init__.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/futures/server.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/futures
> copying src/mpi4py/util/pkl5.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/util
> copying src/mpi4py/util/dtlib.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/util
> copying src/mpi4py/util/__init__.pyi ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.10/build/mpi4py/util
> running build_clib
> MPI configuration: [mpi] from 'mpi.cfg'
> MPI C compiler: /usr/bin/mpicc
> MPI C++ compiler: /usr/bin/mpicxx
> checking for library 'lmpe' ...
> /usr/bin/mpicc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv
> -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g
> -fwrapv -O2 -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -c _configtest.c -o _configtest.o
> /usr/bin/mpicc -pthread -Wl,-z,relro -g -O2
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 _configtest.o -llmpe
> -o _configtest
> /usr/bin/ld: cannot find -llmpe
> collect2: error: ld returned 1 exit status
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/mpi4py_3.1.3-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
mpi4py has been rebuilding fine. Looks like the error experienced in
this bug was transitory, so closing the bug now.
Drew
--- End Message ---
