The tracker currently displays "debian/patches: 1 patch to forward upstream". It should not appear give how the patch is applied upstream pending the next upstream release and the cherry-pick features the Applied-Upstream stanza.

Applied-Upstream: https://github.com/NetworkConfiguration/dhcpcd/commit/25689325f81c7a61bd48f5727eaae1d6f16e1328

Basically, if it's applied upstream, checking for the Forwarded statement is superfluous and it should not print a reminder to submit the patch to upstream.

Martin-Éric

Hi,

FTR here are the relevant links:

Tracker: https://tracker.debian.org/pkg/dhcpcd
UDD: https://udd.debian.org/patches.cgi?src=dhcpcd&version=1%3A10.1.0-4
Patch: https://sources.debian.org/src/dhcpcd/1:10.1.0-4/debian/patches/25689325f81c7a61bd48f5727eaae1d6f16e1328.patch/

I tend to agree with you but this is under control of UDD and AFAIK UDD
is just applying what's documented in DEP-3. There have been suggestions
to update DEP-3 regarding this but nothing happened IIRC. I remember
discussions in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028503

DEP-3: https://dep-team.pages.debian.net/deps/dep3/

The DEP-3 expectation is that you would have added a "Bug" field linking
back to https://github.com/NetworkConfiguration/dhcpcd/issues/398 where it
would have been easy to find your merge request with this patch.

Cheers,

Actually Guillem started a thread in debian-devel after that:
https://lists.debian.org/debian-devel/2023/08/msg00067.html

But no further action happened. I'll possibly try to revive that.

Cheers,

https://salsa.debian.org/qa/udd/-/merge_requests/59 is also relevant - udd
isnt following everything in dep3