Re: Why does tracker/lintian flag 'Origin: upstream' patch as 'to be forwarded'?

To: "Matheus Polkorny" <mpolkorny@gmail.com>, <debian-devel@lists.debian.org>
Subject: Re: Why does tracker/lintian flag 'Origin: upstream' patch as 'to be forwarded'?
From: "Andrea Pappacoda" <tachi@debian.org>
Date: Sat, 20 Sep 2025 18:43:26 +0200
Message-id: <[🔎] DCXS13CJD02C.TR07LIF7AFST@debian.org>
In-reply-to: <[🔎] och6sdhgmzw574nn37dt4kykha5n2zhpkavgoawhwdstfkkngs@5x3yt3wreeya>
References: <[🔎] och6sdhgmzw574nn37dt4kykha5n2zhpkavgoawhwdstfkkngs@5x3yt3wreeya>

Hi Matheus,

On Sat Sep 20, 2025 at 6:07 PM CEST, Matheus Polkorny wrote:

I understand that the tracker might be following the DEP-3 rule as
written, but it seems illogical to flag a patch as
"to be forwarded upstream" when its Origin field already indicates
it came from there.

This is a known issue. See merge request<https://salsa.debian.org/dep-team/deps/-/merge_requests/10> fora proposed solution.


Bye!

Reply to:

References:
- Why does tracker/lintian flag 'Origin: upstream' patch as 'to be forwarded'?
  - From: Matheus Polkorny <mpolkorny@gmail.com>

Prev by Date: Re: [Pkg-rust-maintainers] Bug#1115714: impossible to install crate zerovec: depends on missing librust-twox-hash-2+xxhash64-dev
Next by Date: Re: [Pkg-rust-maintainers] Bug#1115714: impossible to install crate zerovec: depends on missing librust-twox-hash-2+xxhash64-dev
Previous by thread: Why does tracker/lintian flag 'Origin: upstream' patch as 'to be forwarded'?
Next by thread: Bug#1115885: librust-tower-lsp-dev: impossible to install: depends on missing librust-async-codec-lite-0.0+default-dev
Index(es):
- Date
- Thread