Quoting Dominique Dumont (2017-01-08 15:36:34) > On Sunday, 8 January 2017 13:05:14 CET Jonas Smedegaard wrote: > > For the record: As a direct consequence of this bug, licensecheck > > testsuite now ignores some failures that occur only when using the > > Debian fork. > > I guess that you are referring to this commit: > https://anonscm.debian.org/cgit/pkg-perl/packages/licensecheck.git/commit/?id=eee0dfa250409c07fb8369b04e254794f6541389 > where Software::LicenseUtils->new_from_short_name is giving you some trouble > because you rely on a fallback mechanism that is still Debian specific (PR > pending since 2015). > > For the record, Debian version accepts some more short names than upstream's > version. > E.g. BSD-3-clause and expat because I believe they are Debian specific. If > you think otherwise, > feel free to submit a PR upstream.
Here is the full list of patches applied to libsoftware-license-perl: summary_method artistic_1.0_summary apache-2-summary gpl-1-summary gpl-2-summary gpl-3-summary lgpl-2-1-summary lgpl-3-summary lgpl-2-summary summary_test add_or_later_clause add-bsd-3-clause-short-name backward-compat add-expat-short-name add-debian-text-method short-name-fallback Examples you mention seem to be these - each changing a single line: add-bsd-3-clause-short-name add-expat-short-name My concern, and what I call a fork, is functionality deviating substantially from that released upstream. Could you please elaborate on how - in your opinion - the _other_ patches do not cause the resulting package to deviate substantially from upstream project? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
