Hi!

It would be nice if wdiff in Debian could be updated to latest upstream
version, see release announcement below.

As temporary new upstream maintainer, I will go through all Debian wdiff
bug reports and see if anything applies upstream, and I could assist
with Debian packaging too if you want.

Consider using upstream git instead of tarballs as the source, for
better supply-chain auditability, although doing so requires a bit of
work (compare e.g., libntlm or libidn2 packaging for gnulib magic).

/Simon

Simon Josefsson via Bug reports for and general discussion about GNU
wdiff <wdiff-bugs@gnu.org> writes:

We believe that the bug you reported is fixed in the latest version of
wdiff, 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 1144231@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Vila <sanvila@debian.org> (supplier of updated wdiff 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 27 Sep 2026 19:50:00 +0200
Source: wdiff
Architecture: source
Version: 1.2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanvila@debian.org>
Changed-By: Santiago Vila <sanvila@debian.org>
Closes: 1144231
Changes:
 wdiff (1.2.3-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #1144231.
   * Switch watch file to format version 5.
   * Switch copyright file to DEP-5 format.
   * Disable dh_autoreconf and drop debian/clean.
   * Drop "Rules-Requires-Root: no" (default).
   * Drop "Priority: optional" (default).
   * Update standards-version.
   * Update signing-key.asc.
Checksums-Sha1:
 9f6fcf0415745774e623c666baa123a7e151de4a 1816 wdiff_1.2.3-1.dsc
 d30f50a08ff60a0c4d488a26f5d4e3ec56a161f2 1709576 wdiff_1.2.3.orig.tar.gz
 d84ec2ac103c4076c7fac093aae82ae679d12d49 1223 wdiff_1.2.3.orig.tar.gz.asc
 cca36d96baf8972d2e8d57e479bea11ce871c326 6852 wdiff_1.2.3-1.debian.tar.xz
 93d1ee0adda467318f8da47e84e07d7cb20b53ad 5561 wdiff_1.2.3-1_source.buildinfo
Checksums-Sha256:
 0e02208904c0d50ac8e2022a60991e8735cd568e9c2d2a0cdaca54136e9983fc 1816 wdiff_1.2.3-1.dsc
 29a4457eb0ed35c902e6732d71f25e1d6c7fe7fa0eda0fb6c371ed6779b49fd6 1709576 wdiff_1.2.3.orig.tar.gz
 ba2415eb5511dd9f4e102db78000de8f27c66b021ad51668e3afa499a8869f87 1223 wdiff_1.2.3.orig.tar.gz.asc
 dcd42325a750339c8aab3386c7c140e2fa57a724ec3a7db83305a96840d04ac1 6852 wdiff_1.2.3-1.debian.tar.xz
 152ea2fde2cb23860cdc0f20756faef3203957eca8e13841a3cd395396cac213 5561 wdiff_1.2.3-1_source.buildinfo
Files:
 db37673833557596c655799a78dc5cc5 1816 text optional wdiff_1.2.3-1.dsc
 39a99cce3d1525bbaeaae21f4bca97ad 1709576 text optional wdiff_1.2.3.orig.tar.gz
 0ed3cbfd20fa025f32f178e78679e023 1223 text optional wdiff_1.2.3.orig.tar.gz.asc
 831cacf4436a60d5866851e3f37a7e7a 6852 text optional wdiff_1.2.3-1.debian.tar.xz
 686ce1f741395c423f7d436343dc3d30 5561 text optional wdiff_1.2.3-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmq5YMcACgkQQc5/C58b
izLLjggAgEL+8ElUFYTZpkYdF52VTxDpj1swCGkb3SJobVQNOiZojAmJnYO2YGJ4
7FKSbSDxACd3/L4dFhoolbYGjPWZhBEWvADHubxOF6nTQ5RPVOSwbKI9+dqshgZv
ey417HkSHa54qKFQWhASoFKQRfHlnk0fTq6N4MV4gqNLicdnWaz2VZsHeeKnvDxK
OcTWQbchMDbr7SkqaG0Cfzuwkta2UMj6R8k20bCuLszreUsF61DQalBl7DCgFazc
4SoNgDRX46iRgA8cI85WlTCY1kZaWlRhIkRkIbCEM2AMq6sfczeRcZN7ZCHNDU2/
2pb86RElOuHee6rJS3/+QcDoomperg==
=L+A5
-----END PGP SIGNATURE-----

I did not find any special trouble in the packaging, but if you can
review the bug reports in the BTS, that would be great.

Indeed, using git instead of tarballs adds a complexity which I
consider undesired, so I'll keep the traditional tarballs for now.
(Life is too short...)

However, I've done the proper thing with the .sig file and the pgp
keys, so I believe the supply-chain is in a good state. More to the
point, you are not a "Mr. Unknown", you are a known person in the free
software world, and I trust you :-)

Thanks.