Your message dated Wed, 12 Mar 2025 17:19:20 +0000
with message-id <e1tspjk-00ak5h...@fasolo.debian.org>
and subject line Bug#1100195: fixed in beangrow 1.0.0+git20250207-2
has caused the Debian Bug report #1100195,
regarding beangrow: FTBFS: pyproject_hooks._impl.BackendUnavailable: Cannot
import 'setuptools.build_meta'
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 ow...@bugs.debian.org
immediately.)
--
1100195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:beangrow
Version: 1.0.0+git20250207-1
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
dh_autoreconf_clean -O--buildsystem=pybuild
dh_clean -O--buildsystem=pybuild
debian/rules execute_after_dh_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
# Explicitly remove config_pb2.py, we regenerate it
rm -fv beangrow/config_pb2.py
removed 'beangrow/config_pb2.py'
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules binary
dh binary --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
debian/rules execute_before_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
# Regenerate config_pb2.py from .proto file
# See https://github.com/beancount/beangrow/pull/22
/usr/bin/make -C beangrow
make[2]: Entering directory '/<<PKGBUILDDIR>>/beangrow'
protoc -I . --python_out . --proto_path . config.proto
make[2]: Leaving directory '/<<PKGBUILDDIR>>/beangrow'
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build -O--buildsystem=pybuild
I: pybuild plugin_pyproject:129: Building wheel for python3.13 with "build"
module
I: pybuild base:311: python3.13 -m build --skip-dependency-check --no-isolation
--wheel --outdir /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_beangrow
* Building wheel...
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pyproject_hooks/_impl.py", line 402, in
_call_hook
raise BackendUnavailable(
...<4 lines>...
)
pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta'
ERROR Backend 'setuptools.build_meta' is not available.
E: pybuild pybuild:389: build: plugin pyproject failed with: exit code=1:
python3.13 -m build --skip-dependency-check --no-isolation --wheel --outdir
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_beangrow
dh_auto_build: error: pybuild --build -i python{version} -p 3.13 returned exit
code 13
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202503/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:beangrow, so that this is still
visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: beangrow
Source-Version: 1.0.0+git20250207-2
Done: Colin Watson <cjwat...@debian.org>
We believe that the bug you reported is fixed in the latest version of
beangrow, 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 1100...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Colin Watson <cjwat...@debian.org> (supplier of updated beangrow 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 12 Mar 2025 16:56:27 +0000
Source: beangrow
Architecture: source
Version: 1.0.0+git20250207-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Colin Watson <cjwat...@debian.org>
Closes: 1100195
Changes:
beangrow (1.0.0+git20250207-2) unstable; urgency=medium
.
* Team upload.
* Build-depend on python3-setuptools (closes: #1100195).
Checksums-Sha1:
5f497eefa0cfcccb974931d0bd78d449047d2bd8 3314 beangrow_1.0.0+git20250207-2.dsc
82652a397b3ea3a9cb81641679cc4987963c23e6 2204
beangrow_1.0.0+git20250207-2.debian.tar.xz
Checksums-Sha256:
e1ea353da41592f487a27d459192790af3a28565150eba74f7d67805dfe76fc1 3314
beangrow_1.0.0+git20250207-2.dsc
1026e12031275a4c2a406cd706cb0d5f4542f7f385719173d632ffe5816f7f95 2204
beangrow_1.0.0+git20250207-2.debian.tar.xz
Files:
95bfe5c5bf36d9e5d4bc75a9b8c696d8 3314 python optional
beangrow_1.0.0+git20250207-2.dsc
744c8e72c3c49afad4bfb6929d2f67b8 2204 python optional
beangrow_1.0.0+git20250207-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmfRvQUACgkQOTWH2X2G
UAu2FBAAgQFSIRdTgce4ZPaJ+5OepJU0OBt2s7HUx3GRo56sR0c+DC8kanT5pf0y
GGoRZX+ixoiZc4W5OKvzv3/KftExmvH/EAqj65ISf8n7iUtGm80m/zdjAt4sqx3+
aBpWxcGWQp8H5pIFzPJi4pR0p9bBm79LRi92cg7YTOuGO4SIf6b4nJLeFQwLemi5
4Lfmyrayz854fF+ZIXYicdZ+RxHBYIfKfp5ufpWzdY4WzJIZNDzejsJi0oSFfaY5
1zrL66gWCXbSuRzsodeu+y/GMD0eU0mAVLe/wbEOAW7RB5MzxyqgzdsQQIpQiaYn
PVwpZRwAHVZLWA6pH+ahIKQV1ELMIEk7q7pS1tXxjGujdVh67+rtNjSv1cmn4sJy
/K9MYBiSf0nTTI6wN409DdfBfPLaqb5Mk3gF8OLDKjKiOnkBswmjtuh0icDQwUdr
lbSo1QW7mrxizV+mNgmy1fUSk0d+wyh4nHbJUnP+0S1rAW4OCI+aI8mXqLb5WNgo
UF4CUO8dHcMbeTMbnDlFxYpNzNhrBnC3I3DY7DTvS8q7K7Pj35BD0cl0f0TXPje2
3h6L7xljTC6ZME20W6VZ5kogROowZYkjS12kbVjuts39Cpu0oV6QVDFWn0m5DZT2
rCrtwuez6fJcPSxCicOaT2j7iZeK52NZi3gaW5f/QZKD4CM/uTQ=
=Q2j1
-----END PGP SIGNATURE-----
pgpQFTyXBl95D.pgp
Description: PGP signature
--- End Message ---
