Source: dolfinx Version: 2019.2.0~git20200723.696fbc0-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +------------------------------------------------------------------------------+ > | Install package build dependencies > | > +------------------------------------------------------------------------------+ > > > Setup apt archive > ----------------- > > Merged Build-Depends: cmake (>= 3.5), debhelper-compat (= 13), dh-python, > gfortran, chrpath, libboost-chrono-dev, libboost-dev (>= 1.56), > libboost-filesystem-dev, libboost-iostreams-dev, libboost-math-dev, > libboost-mpi-dev, libboost-program-options-dev, libboost-serialization-dev, > libboost-thread-dev, libboost-timer-dev, libeigen3-dev (>= 3.2.90), > libhdf5-mpi-dev, libsuitesparse-dev, libscotch-dev, libxml2-dev, > mpi-default-dev, libpetsc-real-dev (>= 3.7), libpetsc-complex-dev, > libslepc-real-dev (>= 3.7), libslepc-complex-dev, pybind11-dev (>= 2.2.0), > python3-setuptools, python3-petsc4py-real, python3-petsc4py-complex, > python3-slepc4py-real, python3-slepc4py-complex, pkg-config, python3-all-dev, > python3-cffi, python3-pkg-resources, python3-ffcx (>= 2019.2), python3-ffcx > (<< 2019.3), python3-ufl, python3-mpi4py, python3-numba, python3-numpy, > python3-ply, python3-sphinx, build-essential, fakeroot, doxygen, > libjs-mathjax, libjs-modernizr, python3-sphinx-rtd-theme > Filtered Build-Depends: cmake (>= 3.5), debhelper-compat (= 13), dh-python, > gfortran, chrpath, libboost-chrono-dev, libboost-dev (>= 1.56), > libboost-filesystem-dev, libboost-iostreams-dev, libboost-math-dev, > libboost-mpi-dev, libboost-program-options-dev, libboost-serialization-dev, > libboost-thread-dev, libboost-timer-dev, libeigen3-dev (>= 3.2.90), > libhdf5-mpi-dev, libsuitesparse-dev, libscotch-dev, libxml2-dev, > mpi-default-dev, libpetsc-real-dev (>= 3.7), libpetsc-complex-dev, > libslepc-real-dev (>= 3.7), libslepc-complex-dev, pybind11-dev (>= 2.2.0), > python3-setuptools, python3-petsc4py-real, python3-petsc4py-complex, > python3-slepc4py-real, python3-slepc4py-complex, pkg-config, python3-all-dev, > python3-cffi, python3-pkg-resources, python3-ffcx (>= 2019.2), python3-ffcx > (<< 2019.3), python3-ufl, python3-mpi4py, python3-numba, python3-numpy, > python3-ply, python3-sphinx, build-essential, fakeroot, doxygen, > libjs-mathjax, libjs-modernizr, python3-sphinx-rtd-theme > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<<RESOLVERDIR>>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<<RESOLVERDIR>>/apt_archive ./ InRelease > Get:2 copy:/<<RESOLVERDIR>>/apt_archive ./ Release [963 B] > Ign:3 copy:/<<RESOLVERDIR>>/apt_archive ./ Release.gpg > Get:4 copy:/<<RESOLVERDIR>>/apt_archive ./ Sources [708 B] > Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [782 B] > Fetched 2453 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > ---------------------------------------------------- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-numba : Depends: python3-llvmlite (< 0.34) but 0.34.0-1 is to be > installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/09/26/dolfinx_2019.2.0~git20200723.696fbc0-4_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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
