[From nobody Mon Oct 5 16:25:05 2026 Received: (at submit) by bugs.debian.org; 20 Mar 2024 21:06:30 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02 (2021-04-09) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-105.5 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA, FROMDEVELOPER,FVGT_m_MULTI_ODD,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST, USER_IN_DKIM_WHITELIST autolearn=ham autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 42; hammy, 150; neutral, 179; spammy, 0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--Hx-spam-relays-external:sk:stravin, 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311, 0.000-+--H*RT:108 Return-path: <lucas@debian.org> Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:57852) from C=NA, ST=NA, L=Ankh Morpork, O=Debian SMTP, OU=Debian SMTP CA, CN=stravinsky.debian.org, EMAIL=hostmaster@stravinsky.debian.org (verified) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94.2) (envelope-from <lucas@debian.org>) id 1rn38o-00BDm9-2D for submit@bugs.debian.org; Wed, 20 Mar 2024 21:06:30 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:Content-Type:MIME-Version:Message-ID: Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=JSCFu9rVZn7l2YPtYY8SrZItgit917tm4azG3BnlJ3U=; b=sg+/h9CYgE6VeLZpcJM9djqDiv Ns045FGwZI8n7l9utpT9sk6HBYZcbptJnzHu765vR10LFUXG5F8HGKl7+/wwMUdMUdIfRYDqX1pml DAclutE/ucXRltPOfm3PrOXws6Vaj1xD65tPuB0kKDc9F8QqqTCBJ8N35TjTnFwWBNbNO203mcy2O EF/WgW8PPqe/uqfsYx48KhElfa8Z+bEsHqwY8OSDv1CYWtvTkK4zpH7ZEJulCvnYXZdJW6kGwM46P nkO4Ukj0x2kZMyRi745KA+XAg0pbd93fNENfT/7uqDA/p46/dcCah4S9/xmtH6HGV7/MlpBDIxOLT 3HslyujA==; Received: from authenticated user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94.2) (envelope-from <lucas@debian.org>) id 1rn38l-0007Xm-VO for submit@bugs.debian.org; Wed, 20 Mar 2024 21:06:28 +0000 Date: Wed, 20 Mar 2024 21:58:05 +0100 From: Lucas Nussbaum <lucas@debian.org> To: submit@bugs.debian.org Subject: gnucap-python: FTBFS: _gnucap_swig.cxx:4535:10: fatal error: numpy/arrayobject.h: No such file or directory Message-ID: <ZftN3claJjZowRyj@grub.nussbaum.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Debian-User: lucas Delivered-To: submit@bugs.debian.org Source: gnucap-python Version: 0.0.2-1.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lucas@debian.org Usertags: ftbfs-20240319 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../gnucap -I.. -I../../include -I/usr/include/python3.12 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -I/usr/include/gnucap -I/usr/lib/python3/dist-packages -DPYTHON_SO=\"/usr/lib/x86_64-linux-gnu/\" -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o _md.lo _md.cxx > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../gnucap -I.. -I../../include -I/usr/include/python3.11 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -I/usr/include/gnucap -I/usr/lib/python3/dist-packages -DPYTHON_SO=\"/usr/lib/x86_64-linux-gnu/\" -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c _component.cxx -fPIC -DPIC -o .libs/_component.o > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../gnucap -I.. -I../../include -I/usr/include/python3.11 -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -I/usr/include/gnucap -I/usr/lib/python3/dist-packages -DPYTHON_SO=\"/usr/lib/x86_64-linux-gnu/\" -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c _gnucap_swig.cxx -fPIC -DPIC -o .libs/_gnucap_swig.o > libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/13/crtbeginS.o .libs/garbage.o -L/usr/lib/x86_64-linux-gnu -ldl -L/usr/lib/gcc/x86_64-linux-gnu/13 -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/13/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/13/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crtn.o -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-soname -Wl,libgnucap-python.so.0 -o .libs/libgnucap-python.so.0.0.0 > _gnucap_swig.cxx:4535:10: fatal error: numpy/arrayobject.h: No such file or directory > 4535 | #include <numpy/arrayobject.h> > | ^~~~~~~~~~~~~~~~~~~~~ > compilation terminated. > make[6]: *** [Makefile:785: _gnucap_swig.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/19/gnucap-python_0.0.2-1.2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lucas@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240319&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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 mark 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. ]