Bug#1068324: lintian: patch-not-forwarded-upstream for upstream patches

2024-04-20 Thread Nilesh Patra
On Sat, Apr 20, 2024 at 02:57:28PM +, Thorsten Glaser wrote: > >Right. AFAICS, lintian spews that warning because the header in that patch in > >incomplete. It also needs a "From" and "Subject" (which can be same as commit > > this is not entirely correct. > > The full patch header is: > >

Bug#1068324: lintian: patch-not-forwarded-upstream for upstream patches

2024-04-20 Thread Thorsten Glaser
Hi Nilesh, >Right. AFAICS, lintian spews that warning because the header in that patch in >incomplete. It also needs a "From" and "Subject" (which can be same as commit this is not entirely correct. The full patch header is: Description: fix typeset -p confusion between empty and unset Origin:

Bug#1068324: lintian: patch-not-forwarded-upstream for upstream patches

2024-04-20 Thread Nilesh Patra
Hi Thorsten, Quoting mirabilos: > (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): > >

Bug#1068324: lintian: patch-not-forwarded-upstream for upstream patches

2024-04-03 Thread Thorsten Glaser
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: