Source: libseccomp

Version: 2.5.4-1

Tags: bookworm ftbfs

Severity: serious


When I build this package from source, the build fails. Please see log output 
at the end.

My build environment is a container image based on Debian testing bookworm, 
which already includes python3.11



After some research I guess it may be related to the upgrade to pyhton3.11 and 
the new behavior which enforces pip install packages only in venv.

There is also a separation of user und system packages which may be the problem 
in an isolated buildroot.

There maybe a new PEP668 involved: https://peps.python.org/pep-0668/ 
https://peps.python.org/pep-0668/#keep-the-marker-file-in-container-images

https://discuss.python.org/t/python3-m-pip-install-user-broken-in-debian-testing/24268

And a long discussion about distros:

https://discuss.python.org/t/pep-668-marking-python-base-environments-as-externally-managed/10302/72





debuild '' -F -uc -us

dpkg-buildpackage -us -uc -ui -F

dpkg-buildpackage: info: source package libseccomp

dpkg-buildpackage: info: source version 2.5.4-1

dpkg-buildpackage: info: source distribution unstable

dpkg-buildpackage: info: source changed by Felix Geyer 
fge...@debian.org<mailto:fge...@debian.org>

dpkg-source --before-build .

dpkg-buildpackage: info: host architecture amd64

debian/rules clean

dh clean --with python3

   debian/rules override_dh_auto_clean

make[1]: Entering directory '/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4'

dh_auto_clean

rm -f regression.out

make[1]: Leaving directory '/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4'

   dh_clean

dpkg-source -b .

dpkg-source: info: using source format '3.0 (quilt)'

dpkg-source: info: verifying ./libseccomp_2.5.4.orig.tar.gz.asc

dpkg-source: info: building libseccomp using existing 
./libseccomp_2.5.4.orig.tar.gz

dpkg-source: info: building libseccomp using existing 
./libseccomp_2.5.4.orig.tar.gz.asc

dpkg-source: info: building libseccomp in libseccomp_2.5.4-1.debian.tar.xz

dpkg-source: info: building libseccomp in libseccomp_2.5.4-1.dsc

debian/rules binary

dh binary --with python3

   dh_update_autotools_config

   dh_autoreconf

…

…

…

checking for cov-build... no

checking whether to build with code coverage support... no

checking that generated files are newer than configure... done

configure: creating ./config.status

config.status: creating libseccomp.pc

config.status: creating include/seccomp.h

config.status: creating Makefile

config.status: creating include/Makefile

config.status: creating src/Makefile

config.status: creating src/python/Makefile

config.status: creating tools/Makefile

config.status: creating tests/Makefile

config.status: creating doc/Makefile

config.status: creating configure.h

config.status: configure.h is unchanged

config.status: executing depfiles commands

config.status: executing libtool commands

        cd src/python && make -j8 install 
DESTDIR=/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4/debian/tmp 
AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" PYTHON=python3.11

make[2]: Entering directory 
'/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4/src/python'

[ . == . ] || cp ./seccomp.pyx .

VERSION_RELEASE="2.5.4" CPPFLAGS="-I\../../include -I../../include 
-I../../include -Wdate-time -D_FORTIFY_SOURCE=2" CFLAGS="-Wall -Umips -g -O2 
-ffile-prefix-map=/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4=. 
-fstack-protector-strong -Wformat -Werror=format-security" LDFLAGS="-Wl,-z 
-Wl,relro -Wl,-z,relro" python3.11 ./setup.py build && touch build

make[3]: Entering directory 
'/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4/src/python'

VERSION_RELEASE="2.5.4" CPPFLAGS="-I\../../include -I../../include 
-I../../include -Wdate-time -D_FORTIFY_SOURCE=2" CFLAGS="-Wall -Umips -g -O2 
-ffile-prefix-map=/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4=. 
-fstack-protector-strong -Wformat -Werror=format-security" LDFLAGS="-Wl,-z 
-Wl,relro -Wl,-z,relro" python3.11 ./setup.py install 
--install-lib=/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4/debian/tmp//usr/lib/python3.11/site-packages
 \

        
--record=/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4/debian/tmp//usr/lib/python3.11/site-packages/install_files.txt

make[3]: Nothing to be done for 'install-data-am'.

/usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip 
and other standards-based tools.

  warnings.warn(

/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: 
EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
and pip and other standards-based tools.

  warnings.warn(

TEST FAILED: 
/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4/debian/tmp//usr/lib/python3.11/site-packages/
 does NOT support .pth files

bad install directory or PYTHONPATH



You are attempting to install a package to a directory that is not

on PYTHONPATH and which Python does not read ".pth" files from.  The

installation directory you specified (via --install-dir, --prefix, or

the distutils default setting) was:



    
/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4/debian/tmp//usr/lib/python3.11/site-packages/



and your PYTHONPATH environment variable currently contains:



    ''



Here are some of your options for correcting the problem:



* You can choose a different installation directory, i.e., one that is

  on PYTHONPATH or supports .pth files



* You can add the installation directory to the PYTHONPATH environment

  variable.  (It must then also be on PYTHONPATH whenever you run

  Python and want to use the package(s) you are installing.)



* You can set up the installation directory to support ".pth" files by

  using one of the approaches described here:



  
https://setuptools.pypa.io/en/latest/deprecated/easy_install.html#custom-installation-locations



Please make the appropriate changes for your system and try again.

zip_safe flag not set; analyzing archive contents...

__pycache__.seccomp.cpython-311: module references __file__

make[3]: Leaving directory 
'/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4/src/python'

make[2]: Leaving directory 
'/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4/src/python'

make[1]: Leaving directory '/work/tmp/libseccomp_2.5.4-1/libseccomp-2.5.4'

   dh_install

dh_install: warning: Cannot find (any matches for) 
"usr/lib/python3.*/site-packages/seccomp.cpython-*.so" (tried in ., debian/tmp)



dh_install: warning: python3-seccomp missing files: 
usr/lib/python3.*/site-packages/seccomp.cpython-*.so

dh_install: error: missing files, aborting

make: *** [debian/rules:14: binary] Error 25

dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

debuild: fatal error at line 1182:

dpkg-buildpackage -us -uc -ui -F failed













By the way:

There are multiple other python based source packages, which are also failing 
to build in a bookworm based build environment, all with a similar error 
message:

dh_install: warning: Cannot find (any matches for) "usr/lib/python3*" (tried in 
., debian/tmp)

dh_install: warning: python3-pwquality missing files: usr/lib/python3*

dh_install: error: missing files, aborting

make: *** [debian/rules:15: binary] Error 25



These are: libpwquality_1.4.5-1, libprelude_5.2.0-5



For reference: libpwquality already reported here: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033353

For reference: libprelude already reported here: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033553














Reply via email to