Among the 19 debian patches available in version 2.10.0-3 of the package, we noticed the following issues:
commit 56dcf65f8c6754af0698c291d8b0612746aec8fb
Author: Marc Haber <mh+mr-git@zugschlus.de>
Date: Sat Jun 1 12:57:01 2024 +0200
Standards-Version: 4.7.0 (no changes necessary)
commit 05c34484f5215138743ab9858945376a757d1807
Author: Marc Haber <mh+mr-git@zugschlus.de>
Date: Sat Jun 1 12:56:12 2024 +0200
rename patches for a .patch suffix
commit ad7022e4460033332f6681c36540b59da2633b9c
Author: Marc Haber <mh+mr-git@zugschlus.de>
Date: Sat Jun 1 10:42:41 2024 +0200
hopefully fix patch metadata
In the past I have written "Forwarded: no" for patches that are
inappropriate for upstream. This does seem to be incorrect, changed to
"Forwarded: not-needed".
Also, in the past upstream just had a web form to submit patches. The
specification for patch metadata doesnt seem to want to know this, so I
have also changed those to "not-needed". Most of those patches are also
at least Debian related, and upstream hasnt acted on most of them since
2016. I'm not going to pester them again about those pesky details.
commit f86b5b3eaf0f859912281fb31cb5f29122747236
Author: Marc Haber <mh+debian-packages@zugschlus.de>
Date: Sat Jun 1 10:47:10 2024 +0200
prepare new version
![[bug history graph]](https://qa.debian.org/data/bts/graphs/a/atop.png){kind=link}