[From nobody Sun Oct  4 10:13:06 2026
Received: (at submit) by bugs.debian.org; 30 Sep 2026 10:06:20 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-14.9 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_PACKAGE,FORGED_SPF_HELO,FROMDEVELOPER,HAS_PACKAGE,
 KHOP_HELO_FCRDNS,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,
 SPF_SOFTFAIL autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 20; hammy, 150; neutral, 85; spammy,
 0. spammytokens: hammytokens:0.000-+--H*Ad:N*Bug,
 0.000-+--HTo:N*Debian, 0.000-+--H*F:U*doko, 0.000-+--forky,
 0.000-+--HTo:N*System
Return-path: <doko@debian.org>
Received: from einhorn.in-berlin.de ([192.109.42.8]:57303
 helo=einhorn-mail-out.in-berlin.de)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <doko@debian.org>) id 1xBrCd-00ENoJ-2Y
 for submit@bugs.debian.org; Wed, 30 Sep 2026 10:06:20 +0000
X-Envelope-From: doko@debian.org
X-Envelope-To: <submit@bugs.debian.org>
Received: from authenticated.user (localhost [127.0.0.1]) by
 einhorn.in-berlin.de with ESMTPSA id 68UA6FEm1335602
 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT)
 for <submit@bugs.debian.org>; Wed, 30 Sep 2026 12:06:16 +0200
Message-ID: <bda7cf56-1643-44b1-be4f-0f88ebf48a32@debian.org>
Date: Wed, 30 Sep 2026 12:06:15 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird Beta
Content-Language: en-US
To: Debian Bug Tracking System <submit@bugs.debian.org>
From: Matthias Klose <doko@debian.org>
Subject: dolfin doesn't find the pybind11 module during the build
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org

Package: src:dolfin
Version: 2019.2.0~legacy20240219.1c52e83-31
Severity: important
Tags: sid forky

dolfin doesn't find the pybind11 module during the build, however it has 
a build-dependency on that.  So I assume that it is meant to do 
something senseful with that build-dependency.

The build still succeeds, so maybe add a check that some artifacts added 
with that component show up in the packages?


[...]
-- Detecting CXX compile features - done
Traceback (most recent call last):
   File "<string>", line 1, in <module>
     import pybind11; print(pybind11.get_cmake_dir())
     ^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'pybind11'
CMake Warning (dev) at 
/usr/lib/cmake/pybind11/FindPythonLibsNew.cmake:101 (message):
   Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs 
modules
   are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
   the cmake_policy command to set the policy and suppress this warning, or
   preferably upgrade to using FindPython, either by calling it explicitly
   before pybind11, or by setting PYBIND11_FINDPYTHON ON before pybind11.
Call Stack (most recent call first):
   /usr/lib/cmake/pybind11/pybind11Tools.cmake:44 (find_package)
   /usr/lib/cmake/pybind11/pybind11Common.cmake:243 (include)
   /usr/lib/cmake/pybind11/pybind11Config.cmake:257 (include)
   CMakeLists.txt:28 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Deprecation Warning at 
/usr/lib/cmake/pybind11/FindPythonLibsNew.cmake:110 (cmake_policy):
   The OLD behavior for policy CMP0148 will be removed from a future version
   of CMake.

   The cmake-policies(7) manual explains that the OLD behaviors of all
   policies are deprecated and that a policy should be set to OLD only under
   specific short-term circumstances.  Projects should be ported to the NEW
   behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
   /usr/lib/cmake/pybind11/pybind11Tools.cmake:44 (find_package)
   /usr/lib/cmake/pybind11/pybind11Common.cmake:243 (include)
   /usr/lib/cmake/pybind11/pybind11Config.cmake:257 (include)
   CMakeLists.txt:28 (find_package)
]