On 9/3/20 8:37 PM, Felix Delattre wrote: > On 9/3/20 6:22 PM, Sebastiaan Couwenberg wrote: >> When the patch originates from upstream forwarding it makes no sense, >> i.e. the patches should not have a Forwarded header. > > I added the `not-needed` to avoid the linitian `I: > patch-not-forwarded-upstream` message. > I'm happy to remove them and provoke the message.
lintian emitting that tag when Origin is present is dumb, but seems to conform to DEP-3 which documents: " Forwarded [...] If the field is missing, its implicit value is "yes" if the "Bug" field is present, otherwise it's "no". " And: " Origin [...] The field can be optionaly prefixed with a single keyword followed by a comma and a space to categorize the origin. The allowed keywords are "upstream" (in the case of a patch cherry-picked from the upstream VCS), "backport" (in the case of an upstream patch that had to be modified to apply on the current version), "vendor" for a patch created by Debian or another distribution vendor, or "other" for all other kind of patches. " lintian should support the upstream prefix as a condition to not emit the tag. In the mean time adding Bug headers is more appropriate than Forwarded: not-needed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 _______________________________________________ Pkg-grass-devel mailing list Pkg-grass-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel