Your message dated Sat, 19 Apr 2025 00:52:01 -0400
with message-id <87sem4ah3i....@sergiodj.net>
and subject line Re: Bug#1103206: s4cmd: FTBFS: help2man: can't get `--help'
info from ./debian/s4cmd/usr/share/s4cmd/s4cmd.py
has caused the Debian Bug report #1103206,
regarding s4cmd: FTBFS: help2man: can't get `--help' info from
./debian/s4cmd/usr/share/s4cmd/s4cmd.py
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.)
--
1103206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:s4cmd
Version: 2.1.0+ds-3
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 --with python3 --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
S4CMD_PACKAGING=1 python3 setup.py clean
running clean
rm -rf s4cmd.1 .pybuild build *egg-info
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_autoreconf_clean -O--buildsystem=pybuild
dh_clean -O--buildsystem=pybuild
debian/rules binary
dh binary --with python3 --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.13 setup.py config
running config
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
copying s4cmd.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build
running build_scripts
creating build/scripts-3.13
copying and adjusting s4cmd.py -> build/scripts-3.13
changing mode of build/scripts-3.13/s4cmd.py from 644 to 755
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.13/build;
python3.13 -m unittest discover -v
----------------------------------------------------------------------
Ran 0 tests in 0.000s
NO TESTS RAN
create-stamp debian/debhelper-build-stamp
dh_testroot -O--buildsystem=pybuild
dh_prep -O--buildsystem=pybuild
debian/rules override_dh_auto_install
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_bash-completion
S4CMD_PACKAGING=1 python3 setup.py install --no-compile \
--root /<<PKGBUILDDIR>>/debian/s4cmd \
--install-lib /usr/share/s4cmd \
--install-scripts /usr/share/s4cmd
running install
/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:90:
SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html
for details.
********************************************************************************
!!
self.initialize_options()
running build
running build_py
creating build/lib
copying s4cmd.py -> build/lib
running build_scripts
running install_lib
creating /<<PKGBUILDDIR>>/debian/s4cmd/usr/share/s4cmd
copying build/lib/s4cmd.py -> /<<PKGBUILDDIR>>/debian/s4cmd/usr/share/s4cmd
running install_egg_info
running egg_info
creating s4cmd.egg-info
writing s4cmd.egg-info/PKG-INFO
writing dependency_links to s4cmd.egg-info/dependency_links.txt
writing entry points to s4cmd.egg-info/entry_points.txt
writing requirements to s4cmd.egg-info/requires.txt
writing top-level names to s4cmd.egg-info/top_level.txt
writing manifest file 's4cmd.egg-info/SOURCES.txt'
reading manifest file 's4cmd.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 's4cmd.egg-info/SOURCES.txt'
Copying s4cmd.egg-info to
/<<PKGBUILDDIR>>/debian/s4cmd/usr/share/s4cmd/s4cmd-2.1.0.egg-info
running install_scripts
copying build/scripts-3.13/s4cmd.py ->
/<<PKGBUILDDIR>>/debian/s4cmd/usr/share/s4cmd
changing mode of /<<PKGBUILDDIR>>/debian/s4cmd/usr/share/s4cmd/s4cmd.py to 755
Installing s4cmd script to /<<PKGBUILDDIR>>/debian/s4cmd/usr/share/s4cmd
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_installdocs -O--buildsystem=pybuild
dh_installchangelogs -O--buildsystem=pybuild
debian/rules override_dh_installman
make[1]: Entering directory '/<<PKGBUILDDIR>>'
help2man --no-discard-stderr --version-string='2.0.1' \
-n 'Super Amazon S3 command line tool' -N \
-i debian/extra-man-description.txt \
./debian/s4cmd/usr/share/s4cmd/s4cmd.py > s4cmd.1
help2man: can't get `--help' info from ./debian/s4cmd/usr/share/s4cmd/s4cmd.py
make[1]: *** [debian/rules:16: override_dh_installman] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:9: binary] Error 2
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/202504/
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:s4cmd, so that this is still
visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
user debian-rele...@lists.debian.org
usertags 1103206 + bsp-2025-04-brazil
thanks
On Monday, April 14 2025, Santiago Vila wrote:
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
I can't reproduce this problem anymore. It has been fixed by
https://tracker.debian.org/news/1640327/accepted-setuptools-7810-12-source-into-unstable/
.
This probably also means that the workarounds I've added to the other
packages (stdeb, importlab and plip) aren't needed anymore. I'll double
check and remove them.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/
signature.asc
Description: PGP signature
--- End Message ---
