Your message dated Sat, 08 Feb 2025 23:49:14 +0000
with message-id <e1tguzw-008unt...@fasolo.debian.org>
and subject line Bug#1092228: fixed in jwm 2.4.6-2
has caused the Debian Bug report #1092228,
regarding jwm: FTBFS with gettext 0.23.x
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.)
--
1092228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jwm
Version: 2.4.6-1
Severity: important
Tags: ftbfs trixie sid
User: debian...@lists.debian.org
Usertags: gettext-0.23
Dear maintainer:
During a rebuild of all packages in unstable using gettext 0.23.1, which is
available in experimental, your package failed to build:
--------------------------------------------------------------------------------
[...]
make -C po all
make[2]: Entering directory '/<<PKGBUILDDIR>>/po'
Makefile:202: warning: ignoring prerequisites on suffix rule definition
*** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext
version 0.20 but the autoconf macros are from gettext version 0.22
make[2]: *** [Makefile:244: stamp-po] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/po'
make[1]: *** [Makefile:10: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j1 returned exit code 2
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202501/
Notes:
- Many packages may be fixed by using this in configure.in:
AM_GNU_GETTEXT_REQUIRE_VERSION([0.21])
(removing any existing AM_GNU_GETTEXT_VERSION that may exist).
- This bug will be 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.
- If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:jwm, so that this is still
visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: jwm
Source-Version: 2.4.6-2
Done: Samuel Henrique <samuel...@debian.org>
We believe that the bug you reported is fixed in the latest version of
jwm, 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 1092...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Samuel Henrique <samuel...@debian.org> (supplier of updated jwm 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: Sat, 08 Feb 2025 23:08:21 +0000
Source: jwm
Architecture: source
Version: 2.4.6-2
Distribution: unstable
Urgency: medium
Maintainer: Samuel Henrique <samuel...@debian.org>
Changed-By: Samuel Henrique <samuel...@debian.org>
Closes: 1092228
Changes:
jwm (2.4.6-2) unstable; urgency=medium
.
[ Santiago Vila ]
* d/p/gettext_021.patch: Fix build with gettext 0.23 (closes: #1092228)
Checksums-Sha1:
8f6265d1b8f4ccad34b86ca64bfe45b706ef1d7c 1956 jwm_2.4.6-2.dsc
9872ba5ba462b17464000ddff46090c7a3140f01 253235 jwm_2.4.6.orig.tar.gz
5d88f3d55a9b97343c3e4238632e235dfc9f8670 13692 jwm_2.4.6-2.debian.tar.xz
4763fa6435fe478e4ba8a4663f18ce4f56a5465d 10845 jwm_2.4.6-2_amd64.buildinfo
Checksums-Sha256:
e2b31f91d8de5cac72b7a816025fa06c6e20952e6528540c4aae5e3fc4ca2763 1956
jwm_2.4.6-2.dsc
adfdfc6c866852e970145ace58d6adbe3e4722c9413a90b22f8560620391ac7a 253235
jwm_2.4.6.orig.tar.gz
91955e1574eef374dbe0447944a49da0593e655b8c7396dd0b720a5f734508bc 13692
jwm_2.4.6-2.debian.tar.xz
f0effd375fbb72d1b2a3f96c90eddb8932e4c46ca49c70e193773d7b5d7a1040 10845
jwm_2.4.6-2_amd64.buildinfo
Files:
a1c48f048a4342315156cb2bf3d401b4 1956 x11 optional jwm_2.4.6-2.dsc
7ff2301fd5c4c1e2483bac8079ae9ccb 253235 x11 optional jwm_2.4.6.orig.tar.gz
de250abc2c8e2262b2045b1be3749933 13692 x11 optional jwm_2.4.6-2.debian.tar.xz
d46b595ef9f8f25519b95642d04919ac 10845 x11 optional jwm_2.4.6-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEv66eMxqGenyA2Ot49OSs27jQi+AFAmen5EwACgkQ9OSs27jQ
i+CCow/+PEQ3ocm4ISlHKVR2tcl6isaFJKYgGWap0XiUHa4aSEkXZ9nFwZWSSNTG
9XyslbH7dD2R5wmLCUzVG7bNyBi+RWFGtCnaQUl8S4YKkmqrnlttLK5Ihl1vFhw6
VkZ522Tz84rh4SM1Ubs69TD4gRfWCOz12d9P4sjCZz8iYyfmiOE7ygcuak9dG+zb
4Xztw18dvEKutFpRk1YWuJZMg07TmuObhX/AfxuiH3u5DlWH4JJzge9acXgl19DN
b6J4KwYbk94SBi7z2GK9j3fytx1lBzOTjF1SPQzXWo0GbH2ZlkQbrSz9Wbn5+shF
8/rflfY5UW1iPzvcNoZswXD2zpI3wVY2tXjM3DQVh8kaklx1A/u1I0GTIVQ0JE/6
xKihfhrw4N0FrPoICbYqa2J5Cc9/bEHRI5eWJjtTcCIx97OlPVeeimjvZG2QidTb
obhAVDa/0+q+1SST/wjavRiWr4CqqxoRvgBBFh3rDWBf3nbmE3nUmNOA/SV9b7co
uLwJJaaW6CDUIbwVsb0EWJiNZF+4rIMkAsjqgp46um/RJeMObmJjyJhlW2znLOfF
0BYTfD1lE7/1sMlch3pmfVKXVgETTYfgZSYOTucgQkRX5MhHpI5fo+LhkCOQR3WM
EFgJ+wXthlaH6SvB5j1Rmnpv3lKdqs/XkNFp2DoJtpp09RZG1cE=
=Dgs/
-----END PGP SIGNATURE-----
pgp6179QfI41Q.pgp
Description: PGP signature
--- End Message ---
