Quoting Dominique Dumont (2020-01-12 19:23:54) > This error is triggered by the "and/or" string in the license > short_name. This "and/or" is produced by licensecheck (used by cme > when updating copyright data).
Yes, licensecheck deliberately uses "and/or" when it is uncertain if the user must comply with _both_ licenses or they are permitted to pick _either_ of them. > Since libconfig-model-dpkg-perl 2.124 (released in July 2019), cme > contains code to replace 'and/or' with plain 'or' so the resulting > license short name complies with debian copyright format. It worries me that cme is making such blind assumptions about licensing relationships! > First, licensecheck does not parse correctly the files containing this style > of license specification: > # License: BSD 3 clause > > licensecheck should produce 'BSD (3 clause)' instead of 'BSD (unspecified)' [...] > Jonas, can you check what's going on with licensecheck ? Please file bugs against licensecheck, and reference them when mentioning them elsewhere - e.g. in convoluted bugreports like this. I will happily examine closer, but not easy to handle from within this other bugreport. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
