Hello, I have a question about the `Forwarded` field in the DEP-3 policy and its interaction with tracker. I've observed two examples that seem to behave differently, even though both have `Origin: upstream`: 1. For the visp package, the patch `Fix-build-on-some-architectures.patch` [1] was created after a bug report was filed, then corrected by upstream, and finally added to the package. 2. For the nethogs package, the patch `10-meson-fix-library-name.patch` [2] also came from upstream, but there was no need to file a bug as the fix already existed. My confusion is that tracker [3] shows the message "1 patch to forward upstream", which seems incorrect. The DEP-3 says: "Forwarded: If the field is missing, its implicit value is 'yes' if the 'Bug' field is present, otherwise it's 'no'". In the nethogs case, the patch originated from upstream, so it shouldn't be flagged as "to be forwarded". 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. **References** [1] https://udd.debian.org/patches.cgi?src=visp&version=3.6.0-5 [2] https://udd.debian.org/patches.cgi?src=nethogs&version=0.8.8-2 [3] https://tracker.debian.org/pkg/nethogs -- Thanks, Polkorny
Attachment:
signature.asc
Description: PGP signature