Package: qa.debian.org
Severity: normal
User: qa.debian....@packages.debian.org
Usertags: udd
Hi!
The new patch data is great, thanks! I just noticed though that it does
not recognize a "yes" value for the Forwarded field, while the
"Patch Tagging Guidelines" has this to say about it:
* 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).
So it says that any value other than "no" or "not-needed" means
forwarded, then it says that if the field is missing it means it is an
implicit value of "yes", where I've always interpreted as implicitly
stating that "yes" is also a valid value.
(I also recently amended the patch metadata header template generated
by dpkg-source and did not have "yes" as a value there, but I've added
it locally now, and will probably queue it for dpkg 1.22.x.)
Thanks,
Guillem
