Your message dated Sun, 29 Oct 2023 15:19:05 +0000
with message-id <[email protected]>
and subject line Bug#1033641: fixed in libseccomp 2.5.4-2
has caused the Debian Bug report #1033641,
regarding libseccomp failing to build from source on bookworm with python 3.11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1033641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033641
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
[email protected]<mailto:[email protected]>
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
--- End Message ---
--- Begin Message ---
Source: libseccomp
Source-Version: 2.5.4-2
Done: Felix Geyer <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libseccomp, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Felix Geyer <[email protected]> (supplier of updated libseccomp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 29 Oct 2023 15:13:08 +0100
Source: libseccomp
Architecture: source
Version: 2.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Kees Cook <[email protected]>
Changed-By: Felix Geyer <[email protected]>
Closes: 1033641 1050659 1054788
Changes:
libseccomp (2.5.4-2) unstable; urgency=medium
.
* Fix watch file. (Closes: #1050659)
* Dynamically skip autopkgtests when the test runner already applies seccomp
restrictions.
- Drop isolation-machine restriction.
* Fix FTBFS with setuptools. (Closes: #1054788, #1033641)
- Add python_Fix_distutils_DeprecationWarning.patch
- Add python_single_version_externally_managed.patch
- Explicitly build-depend on python3-setuptools
Checksums-Sha1:
91f8beddfd52672ccebb3ee89aadd00924963535 2708 libseccomp_2.5.4-2.dsc
bcc15f9f7d7fcfa9b05077c0dac8f01e85884c09 17584 libseccomp_2.5.4-2.debian.tar.xz
Checksums-Sha256:
48e3d00b42f561caafddc9149b514234c52f067ea05dd6c6c35c984a5a48c7f4 2708
libseccomp_2.5.4-2.dsc
0b9d98cdc5c9be32652733c08f11d8b788b229e427aa4b2d31df5fc523d498df 17584
libseccomp_2.5.4-2.debian.tar.xz
Files:
840528c538eab3a5d80a23e8769ec70a 2708 libs optional libseccomp_2.5.4-2.dsc
5428cd8e9250fb8cbc248f1bb91c4bbb 17584 libs optional
libseccomp_2.5.4-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAmU+dfkACgkQ/iLG/YMT
XUWh+hAAoKCEMXG3RGuNYAgPLVoda2IFOohAbhIrSOftt9P26UcxO//si9x3PfX6
BGhRo66d1iefaP7+opsHh3vYtYiz616gDtB2EyvlYB+DXz0Vp2U7FRhekS20wazB
1o+jVbwaN09ZWOMI2fNVdTXRc79qKhMvMhHc1V+icGyyLtOPMg2PUGbUzZHnaJ5Y
zAAk22DXMVBIANPKKVfWYwRiWyYJQu1ZJTqSM+0gatxgvGrjOkE3Kex+l5Agfdln
U/a+M8EZXnX6tCGURCVQtwWT67nqqOTReEZLwj+0A4XpzEJhisXvlRLYUEme0k2L
uesrnSFW3s2YaFJ1hsvnlS9HoPZ9kR8R3iMdSIFJrAnpPBtHbzGN2Vtxk12lIQ7d
iUDtJxHrunf2kM/dZS77XT27zV2eEZ0V99i3TfTezhh5yqt5CIVzE4Njx/OSC33Z
pbx4cIWSIHSiZrw8TEucYad/qFMPInNFPLe1ciLBUxy4cud+cIpx4aAphapcaKAv
pIvRYf+VHntkG8zgMx9u7orW+sDtm666WuBeC5Qgvz1xSfO68LWE8dkH42k9t6Ej
QnPNsoRKVHdpSe5TVgl6m97xW389sq+WXeWwdKgQ3E7ZFoUbkK8SLK2DGIO7fZ6Y
MGh4gJ2PAr7f2rG6zz1ZEIZhTSbNhl3XaEzQ8O5bk3k/z13nM8o=
=f8md
-----END PGP SIGNATURE-----
--- End Message ---
