Control: retitle -1 UDD/patches: handling of Forwarded is more strict than DEP-3
On 03/06/25 at 08:21 +0200, Marc Haber wrote: > Package: qa.debian.org > Severity: normal > User: qa.debian....@packages.debian.org > Usertags: udd > > Hi, > > https://udd.debian.org/patches.cgi?src=atop&version=2.11.1-3 flags two > patches having an "invalid" forwarded field. Those two patches have > Forwarded: via web form > in their headers. Upstream used to have a custom web form to submit bug > reports and patches without a visible user database behind it. Hence, I > cannot put an URL here. The web form doesn't exist any more, Upstream is > using github now. > > DEP-3 says: > > Forwarded (optional) > > Any value other than "no" or "not-needed" means that the patch has > been forwarded upstream. Ideally the value is an URL proving that it > has been forwarded and where one can find more information about its > inclusion status. > > If the field is missing, its implicit value is "yes" if the "Bug" > field is present, otherwise it's "no". The field is really required > only if the patch is vendor specific, in that case its value should > be "not-needed" to indicate that the patch must not be forwarded > upstream (whereas "no" simply means that it has not yet been done). > > I therefore believe that "Forwarded: via web form" is NOT invalid, but > valid and allowed usage for the Forwarded: header and that UDD is being > overzealous here. Hi Marc, Ack. See also #1043043 and #1034102, that are related Lucas
