On 21.05.25 22:53, Santiago Vila wrote:
Hi. I've adopted this package today.


Great to hear, thanks for your efforts!


I've checked and the orig.tar.gz that we distribute as 2.85
matches exactly the tar.bz2 that can still be obtained
from sourceforge as 2.85.

Apparently the author took 2.84, updated the license to
"artistic license 2.0" and released it as 2.85 without
raising the version number that "razor-check -v" shows.

I'm retitling the bug to better reflect the problem.

The discrepancy happens only between sourceforge version 2.85
and what the new github repo calls version 2.85 (which is
essentially sourceforge 2.85 + perl cleanups).

So now I understand where the confusion is coming from. I didn't know that
on SF there is also a 2.85 since I was primarily looking at CPAN which IMO is the canonical source for anything Perl. And there the 2.85 version is the code
from GitHub.

Everything taken together I'd still say that this is 2.84, just with an updated
license. Maybe the confusion could be cleared by changing the version to
2.85+really2.84?


The whole mess will be cleared up with a bump to 2.86 past trixie. Do you
need help with that? I looked into that before but got distracted. I think
most of the debian patches were obsolete by now. For a variant of one of
them there is this stalled PR upstream: https://github.com/toddr/Razor2-Client-Agent/pull/11


Am I right to think that what you call IPv6 change is the
same I see when I do "git show -w a2ec2fb" in the github repo?


Yes, it was this issue I filed and fixed https://github.com/toddr/Razor2-Client-Agent/issues/12


If yes, that's a very small change and we don't need to
switch to the new upstream version for that. Can you
backport the change to our current 2.85 version and file
a new (wishlist) bug for that?


Will do.


Thanks,

Malte

Reply via email to