Your message dated Sat, 06 Jun 2026 11:21:46 +0000
with message-id <[email protected]>
and subject line Bug#1126965: fixed in enca 1.21-1.1
has caused the Debian Bug report #1126965,
regarding enca: FTBFS with gettext 0.26
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.)


-- 
1126965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126965
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:enca
Version: 1.21-1
Tags: forky sid ftbfs
User: [email protected]
Usertags: gettext-0.26

Dear maintainer:

During a rebuild of all packages in unstable using gettext 0.26
(yet to be uploaded for Debian), 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/gettext/build-logs/

I've written this page to explain how to reproduce the problem:

https://people.debian.org/~sanvila/gettext/

This bug will be raised to important once gettext is uploaded for
experimental, and RC once gettext is uploaded for unstable, but
I still don't know when I will be able to do that. If you fix
this bug, it would help to have gettext in unstable sooner.

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 cannot 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:enca, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
m4/libiconv.m4:53: warning: macro 'AM_ICONV' not found in library
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
m4/libiconv.m4:53: warning: macro 'AM_ICONV' not found in library
configure.ac:104: warning: The macro 'AC_HEADER_STDC' is obsolete.
configure.ac:104: You should run autoupdate.
./lib/autoconf/headers.m4:663: AC_HEADER_STDC is expanded from...
configure.ac:104: the top level
configure.ac:106: warning: The macro 'AC_HEADER_TIME' is obsolete.
configure.ac:106: You should run autoupdate.
./lib/autoconf/headers.m4:702: AC_HEADER_TIME is expanded from...
configure.ac:106: the top level
configure.ac:138: warning: The macro 'AC_TRY_LINK' is obsolete.
configure.ac:138: You should run autoupdate.
./lib/autoconf/general.m4:2918: AC_TRY_LINK is expanded from...
m4/typevar.m4:7: ye_CHECK_VAR_PROGRAM_INVOCATION_SHORT_NAME is expanded from...
configure.ac:138: the top level
configure:18446: error: possibly undefined macro: AM_ICONV
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: error: /usr/bin/autoconf failed with exit status: 1
dh_autoreconf: error: autoreconf -f -i returned exit code 1
make: *** [debian/rules:16: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2
--------------------------------------------------------------------------------

--- End Message ---
--- Begin Message ---
Source: enca
Source-Version: 1.21-1.1
Done: Reinhard Tartler <[email protected]>

We believe that the bug you reported is fixed in the latest version of
enca, 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.
Reinhard Tartler <[email protected]> (supplier of updated enca 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 06:45:41 -0400
Source: enca
Architecture: source
Version: 1.21-1.1
Distribution: unstable
Urgency: medium
Maintainer: Syed Shahrukh Hussain <[email protected]>
Changed-By: Reinhard Tartler <[email protected]>
Closes: 1126965
Changes:
 enca (1.21-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Santiago Vila ]
   * Fix FTBFS with gettext 0.26. Closes: #1126965
Checksums-Sha1:
 397de78fdd2c99eb1dbc25900cf563fa516a8752 1958 enca_1.21-1.1.dsc
 5c01ed73314877b3f67869f2b5f1e0a80e950682 5644 enca_1.21-1.1.debian.tar.xz
 4ee43e140cd28deafecedead8983a7cb5f87c95c 7035 enca_1.21-1.1_source.buildinfo
Checksums-Sha256:
 151d3996ee3166e632c3b41f19b3d42f389f011c7069a7bb1959d8c3dace9e3b 1958 
enca_1.21-1.1.dsc
 2f06e8b283cee06b68e23a2e53ff756b54c2f3a0d659e8b0c8a41cd0a45ca149 5644 
enca_1.21-1.1.debian.tar.xz
 935ba49e8cb04495bba609c76173e4940a211e990bfd96e011260237eb62880d 7035 
enca_1.21-1.1_source.buildinfo
Files:
 f972955b542a7b73ff4e3647308691b0 1958 text optional enca_1.21-1.1.dsc
 6fa4570d80fec570e1186460e20a8f46 5644 text optional enca_1.21-1.1.debian.tar.xz
 eb7dc39a34dd5bd8c6033fce923fbccb 7035 text optional 
enca_1.21-1.1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmohWH4UHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJstxPBAAiaGm5uKzu7rJBFHUbmyqICM129NV
6RngcJMK3kmDLtIwW7Wf6ApQSqK+qOtYpgY0tQBqvJBoiDr2pxj6/TpBXHSM7+ZQ
6YusWcNqCSmoFZCxxCkB1tNut3m/ZlkPOCmwyV7Bv2s5a0N4uccDWMoAqW5kKh1I
r8aMak8vva0wiZYtyBYqj6Mm1EwqJVmz+Zhi+7WGaov1bLqJqC6ofXL4aY4Bf+m5
MCUMZn8MYR/0S7dmr0PSxCcDf6vnaefX6lJlTEWSJM5z1n4OZe6SMeLaKRF5nljE
jis36lMkhtoiuHnNOXpAlSgTug9oZ9epjvGfGTle3f3pJM1iPNW3Mo9rIxZcC61T
SuN5d8W6nmhNyQT1WhkeC4Pm3z0gzIITRlMzczFo921ONUYotJ1kMrQ3Ee2xHs1x
PfLps5yiHYrXcmxnzS8TcLeAudVmKwT7pcKSpe/N+Xteh22rGgH2cKWTc4NL0EsV
z7fJLnR4akQ9btvyrxC1fK5sMOrYwNl72bIxbt7VE6DiDppQQVxLNvIM4zS15FB5
c2VCWwjn2NnKENovOSk1HpU1VNc+AsbJgrefNo74vOs9ErQjbFkWzHKpdz7ECkZs
VeJfK+37ZMH0JR1OKpVIB60dnCE63GXXwfWex286DYy7j37Mpv+Ey5vChOGt878q
gQvk/m54iPK8Pdk=
=zpMJ
-----END PGP SIGNATURE-----

Attachment: pgp_qECAKvsjT.pgp
Description: PGP signature


--- End Message ---

Reply via email to