Package: release.debian.org Severity: serious User: release.debian....@packages.debian.org Usertags: binnmu
dolfin has started to FTBFS, see https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/dolfin_2018.1.0.post1-13.rbuild.log.gz The dolfin build error comes from mpi4py. The dolfin build succeeds when made with mpi4py rebuilt against with cython 0.29.2-2. Current mpi4py was built with cython 0.28.2-4. The new cython version was uploaded in January. The problem is discussed some more at https://bitbucket.org/mpi4py/mpi4py/issues/112/ For the forthcoming Debian release, it is sufficient to rebuild mpi4py against cython 0.29.2-2 (then we can rebuild dolfin), so please trigger the binNMU. I've marked this bug as "serious" since it involves a FTBFS (of dolfin). nmu mpi4py_2.0.0-3+b2 . ANY . unstable . -m "Rebuild against cython 0.29.2" -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
