On Fri, Mar 16, 2018 at 10:44 PM, Paul Wise <pabs@debian.org> wrote:
I have made a few changes: https, use the new list, reference
debian/copyright directly, add license-violation tag.
I think it is ready to add to the bugs section.
OK; added.
On further reflection, though ... should this actually be split into two: "RFN violation" for fonts that need to be renamed due to the upstream RFN (when the build does not produce bit-identical binaries) plus "RFN missing" for packages where the RFN notice has disappeared?