Your message dated Thu, 20 Mar 2025 10:13:38 +0800
with message-id <bd97f9a26f9092d5d8d3b9a3b722a7efa091b660.ca...@debian.org>
and subject line Re: Bug#1068324: lintian: patch-not-forwarded-upstream for
upstream patches
has caused the Debian Bug report #1068324,
regarding lintian: patch-not-forwarded-upstream for upstream patches
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.)
--
1068324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.116.3
(at least bookworm’s) lintian complains about…
I: mksh source: patch-not-forwarded-upstream [debian/patches/typeset-p-fix.diff]
… for patches whose DEP 3 metadata clearly state they are a
cherry-pick or backport from upstream.
Here (cherry-pick):
Origin: commit:10065BC69BE555D6721
DEP 3 says the Forwarded header is only applicable for
patches that don’t originate upstream.
bye,
//mirabilos
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.117.1
Done: Nilesh Patra <nil...@debian.org>
signature.asc
Description: This is a digitally signed message part
--- End Message ---
