<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Jonas,</p>
<div class="moz-cite-prefix">On 6/16/21 2:50 AM, Jonas Smedegaard
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:162382261691.243380.14702835374663597777@auryn.jones.dk">
<pre class="moz-quote-pre" wrap="">Quoting Walter Lozano (2021-06-16 04:12:23)
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 6/15/21 9:17 PM, Jonas Smedegaard wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Quoting Walter Lozano (2021-06-15 20:42:53)
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">As as user of licensecheck I found it does not provide
deterministic results on some circumstances. And example of this is
gnutls28/m4/ax_code_coverage.m4 which is detected as UNKNOWN or
LGPL.
After some debugging I found that the root cause could be in
libregexp-pattern-license-perl, I have proposed a fix which you
can find in
<a class="moz-txt-link-freetext" href="https://salsa.debian.org/perl-team/modules/packages/libregexp-pattern-license">https://salsa.debian.org/perl-team/modules/packages/libregexp-pattern-license</a>-
perl/-/merge_requests/1
I hope you can help me to clarify this issue.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Great - thanks a lot!
I suspect that this might be bug#982849.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Yes, it looks exactly the same issue I faced. I hope you can confirm
and fix it
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I will certainly do that.
</pre>
</blockquote>
In relation to this, I find that the problem is more evident at
least after these commits, which are related to versioning<br>
<br>
<span class="transaction-comment" data-sigil="transaction-comment"
data-meta="0_7">
<ul class="remarkup-list">
<li class="remarkup-list-item">eddc64dd1f0e6f9bd1769ef580a217aa4be762b8
(synthesize subject pattern name: optimize version matching)</li>
<li class="remarkup-list-item">cd75d77da201260bc9deef4631d5c4d3a42fa41d
(add license patterns lgpl_2 lgpl-2_1 lgpl-3)</li>
</ul>
</span>I hope this information is useful.
<blockquote type="cite"
cite="mid:162382261691.243380.14702835374663597777@auryn.jones.dk">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Please keep all conversation about the bug here - *not* at salsa.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Perfect, I will do that. To be honest I was not sure how to submit the
proposed fix, I also tried to submitted directly to
<a class="moz-txt-link-freetext" href="https://salsa.debian.org/build-common-team/regexp-pattern-license">https://salsa.debian.org/build-common-team/regexp-pattern-license</a>
but I was not able to see a way to send a MR.
Please advice what is the best way to contribute.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Sorry, I am aware that reporting issues can be confusing, and am happy
that you figured out _some_ way to get your findings across.
I use salsa.debian.org as a place to publicly store the git repo but
*not* to track issues or negotiate change proposals or run continuous
integration tests or any other of the many things that Gitlab can do.
I use bugs.debian.org to track issues.
Best way to report and discuss issues is to use bugs.debian.org, and
best way to propose a change is to attach a patch to an email sent to an
issue tracked in bugs.debian.org.
As you are already aware, some parts of Licensecheck is maintained in
other libraries. Git repos exist separately for Debian packaging and
upstream development of these libraries, but that should not matter for
issue tracking.
E.g. <a class="moz-txt-link-freetext" href="https://metacpan.org/dist/App-Licensecheck/view/bin/licensecheck">https://metacpan.org/dist/App-Licensecheck/view/bin/licensecheck</a>
and <a class="moz-txt-link-freetext" href="https://metacpan.org/dist/App-Licensecheck">https://metacpan.org/dist/App-Licensecheck</a> links to
<a class="moz-txt-link-freetext" href="https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=licensecheck">https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=licensecheck</a> for issue
reporting, and <a class="moz-txt-link-freetext" href="https://www.debian.org/Bugs/Reporting">https://www.debian.org/Bugs/Reporting</a> covers issue
reporting in Debian.
I find it unhelpful that salsa.debian.org by default enables duplicate
issue tracking services, and I disable those to limit the risk of
confusion - but sometimes I forget that, and also sometimes others that
I collaborate with may disagree and (re)enable them.
If you have suggestions for ways I could maybe improve communicating how
to best report issues, then please do share.
</pre>
</blockquote>
<p>Thanks for clarifying, and for taking the time to investigate the
issue. Next time I will send you a patch as an attachment.</p>
<p>Regards,</p>
<p>Walter<br>
</p>
</body>
</html>