commit 15512eefe2e3d2a0269591bff095b8a387ae4fc8
Author: Manuel Jacob <me@manueljacob.de>
Date: Sun Apr 19 22:31:57 2026 +0200
Remove misleading comment.
I saw the message “Too much input for diff” in the output. Searching for that in the source code lead me to this config parameter. In that context, reading the comment made me think that GNU diffutils has some hard limit. Manual testing showed that `diff` can cope with much larger files. I thought that maybe there used to be some hard limit. I couldn’t find anything like that when skimming GNU diffutils changes.
When diffing two files with few differences, I found the memory usage to be about the sum of the size of the input files. When constructing inputs that caused more than 2GiB of memory usage, the command didn’t finish after 1 h. Surely, there are cases where GNU diffutils could use less RAM or handle large files better, but fundamentally it is an issue of limited hardware resources.
In conclusion, I think that the comment is more misleading than insightful. I couldn’t think of a better one that states more than the obvious (“resources are limited”), so I decided to remove it.
commit 2278504318fabe4a85ac57b84297c4b086be21f3
Author: Chris Lamb <lamby@debian.org>
Date: Fri Apr 10 11:41:45 2026 -0400
Bump Standards-Version to 4.7.4.
commit a8811c5dd37dd7085e8fb0a3c5aa1738a427bc0e
Author: Chris Lamb <lamby@debian.org>
Date: Fri Apr 10 11:41:42 2026 -0400
Open new changelog entry for version 318.
Gbp-Dch: ignore
There is 1 open security issue in bookworm.
You can find information about how to handle this issue in the security team's documentation.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/d/diffoscope.png){kind=link}