Your message dated Thu, 04 Jun 2026 02:33:51 +0000
with message-id <[email protected]>
and subject line Bug#1136751: fixed in lrzsz 0.12.21rc-1
has caused the Debian Bug report #1136751,
regarding lrzsz: FTBFS with autoconf 2.73
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.)
--
1136751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136751
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:lrzsz
Version: 0.12.21rc-0.3
Severity: serious
Tags: forky sid ftbfs
User: [email protected]
Usertags: autoconf-2.73
Dear maintainer:
During a rebuild of all packages in unstable (using autoconf 2.73,
already in unstable) this package failed to build.
Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:
https://people.debian.org/~sanvila/build-logs/autoconf-2.73/
When fixing this bug, please check that the package also builds
with gettext 0.26, which is already in experimental.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
test -f src/lrz.c && test -f debian/rules
[ ! -f Makefile ] || /usr/bin/make clean
dh_autoreconf_clean
dh_clean
rm -rf debian/tmp
rm -f build-stamp po/lrzsz.pot po/*.gmo debian/substvars
debian/rules binary
test -f src/lrz.c && test -f debian/rules
touch config.rpath
dh_autoreconf
autoreconf: export WARNINGS=
autoreconf: warning: autoconf input should be named 'configure.ac', not
'configure.in'
autoreconf: Entering directory '.'
autoreconf: running: autopoint --force
autopoint: *** The AM_GNU_GETTEXT_VERSION declaration in your configure.in
file requires the infrastructure from gettext-0.10.32 but this
version
is older. Please upgrade to gettext-0.10.32 or newer.
autopoint: *** Stop.
autoreconf: error: autopoint failed with exit status: 1
dh_autoreconf: error: autoreconf -f -i -v returned exit code 1
make: *** [debian/rules:33: build-stamp] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit
status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: lrzsz
Source-Version: 0.12.21rc-1
Done: Martin A. Godisch <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lrzsz, 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.
Martin A. Godisch <[email protected]> (supplier of updated lrzsz 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: Thu, 04 Jun 2026 03:24:56 +0200
Source: lrzsz
Architecture: source
Version: 0.12.21rc-1
Distribution: unstable
Urgency: medium
Maintainer: Martin A. Godisch <[email protected]>
Changed-By: Martin A. Godisch <[email protected]>
Closes: 1126976 1136751
Changes:
lrzsz (0.12.21rc-1) unstable; urgency=medium
.
* Fix FTBFS with gettext 0.26 / modern autopoint. configure.in used
AM_GNU_GETTEXT without any version declaration, so autopoint assumed the
obsolete gettext-0.10.32 infrastructure and aborted autoreconf. Add new
patch gettext_require_version.diff declaring
AM_GNU_GETTEXT_REQUIRE_VERSION([0.19.8]), closes: #1126976, #1136751.
* The modern gettext infrastructure pulled in that way needs po/Makevars
and po/LINGUAS, which upstream never shipped. Add both via new patch
po_makevars_linguas.diff (LINGUAS lists "de" to keep the German
catalogue).
* Make "debian/rules clean" idempotent. dh_autoreconf installs automake's
maintainer-mode rebuild rules, so a second build re-ran automake during
"make clean" and failed (automake >= 1.16 rejects the old configure.in).
Neutralise ACLOCAL/AUTOCONF/AUTOMAKE/AUTOHEADER for that clean invocation.
* Also remove the configure/config.status output (Makefile, config.h,
config.status, sub-directory Makefiles, Specfile, systype, ...) in the
clean target. "make clean" left these behind, so a rebuild aborted in
dpkg-source -b with unexpected changes to the 3.0 (quilt) tree.
* Fix the remaining C compiler warnings via new patch compiler_warnings.diff:
a real -Wformat= bug in src/lsyslog.c (int passed for %ld) and the
-Wunused-result warnings for write()/system()/vasprintf() in src/.
Checksums-Sha1:
d1f761253dd3870186c37b8c34ed50cfc7844f09 1765 lrzsz_0.12.21rc-1.dsc
530518a60827ad2b3e320ec58c13869bde9a5c2e 20224 lrzsz_0.12.21rc-1.debian.tar.xz
9bb42fe4f6c69fc6daa60161f71f133e9de2afd4 5581 lrzsz_0.12.21rc-1_amd64.buildinfo
Checksums-Sha256:
7e275247224854acfe22b6168b4bc127f1bd246730c88b5363eacda6cc8fedcf 1765
lrzsz_0.12.21rc-1.dsc
05cce40bf3ab3f8e0ac3e65a971b4c4cbbd9c29f70596efa6f9634e231604508 20224
lrzsz_0.12.21rc-1.debian.tar.xz
4f64ecf6f60af55faac996434e4a7ce1a9fd62a5dc94c51a79af9c3f0529cb1c 5581
lrzsz_0.12.21rc-1_amd64.buildinfo
Files:
bb846579c857565252dc76e929472b7c 1765 comm optional lrzsz_0.12.21rc-1.dsc
da2bb59180aa51f155e4bfea2e7d982e 20224 comm optional
lrzsz_0.12.21rc-1.debian.tar.xz
35c3d7c6e42df0b54ad00a1744d7ce93 5581 comm optional
lrzsz_0.12.21rc-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJHBAEBCgAxFiEEGEIyO0/Pm5CZX6F/o1C5kfBaSFcFAmog1IgTHGdvZGlzY2hA
ZGViaWFuLm9yZwAKCRCjULmR8FpIV0lIEACLaRfY9PUtdWeZPhbH0vl2tYbNVGPe
iVNyz4p8u3sNkuFB0HfQa+5I6H5BVo3eocs3/ZZzqkHimbUZhWp18u++lDjD1DFY
ERE++iF1TYk8q3dWnIOFN9P6dSTnQYZ6Yo9mw9xyFDxrhzxagltV3jLS8l2YERuG
kxJQVk9Jb4KFEYWy9CJjOEGvtTPA/sqDReMzHEprcUzxSBV1BK0bc5dj/ephUXyz
MMQl0ODksj1S56YrDZH2NBqP+BXK/IKZhns0Mp6BK6vbJOZIGubnrkaYjbh5oy6f
YZXnOupZF+gNOp0UHFNA42KPGb8TxUWNvP6XH8E5o0FrE4H96qcGGNpR27pmKUt+
9/HSTbfGybhSt+zrDb/4IK6CygkXv2nQpQ9KI8Xgo+x5yFUfTJF1izdazX0d/gq8
jhrMku3Rt4iaSRQyik00+xqRjEcadTXoL2aVKNzga8yA65oeBnnauxGjEquk02s8
xvnnl5dU0Op1yI12HW765CP+Zxyzl0SnWpXRNpf23fMUyPM7SKao8Mx0hqaRd1ge
HAEpLqW4wRwzwe36DLcelBK5ctGH99hTOSm7s2lc7SwZppkMVunY4gEqGtyEHHt+
veA0ksM/fn2wDhlATFx00v6hYSHQI8VkY9GWFWKN7020nWMCVxwz2N/OT6z19QXZ
dhPtJCu2DGkIWw==
=/Nn4
-----END PGP SIGNATURE-----
pgpo6aFgwF3fs.pgp
Description: PGP signature
--- End Message ---
