El 26/5/25 a las 11:06, Malte S. Stretz escribió:
On 21.05.25 22:53, Santiago Vila wrote:
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 current version is 2.85 and it was meant to be 2.85, it's just that the
author
forgot to update the version in several other places.
Sometimes authors increase the version for minor changes like updated licenses
and the like.
So, it's not that "it's really 2.84". It just mistakenly identifies itself
as 2.84. This is why I changed the bug title, and I don't see the need
to change the version at this point. It may be confusing, but not to the
point that it needs a version change on our (Debian) side.
The whole mess will be cleared up with a bump to 2.86 past trixie.
Yes. I'll keep this open until then. Sometimes an open bug is the
best way to document something like this. It would be a "wontfix",
which is our way to say that the cure is worse than the disease,
but I don't like using the tag, as this will eventually be fixed.
Do you need help with that?
Not particularly, but I take note that you can help if required.
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?
Note that since I've decided not to include the IPv6 change
for trixie, it is likely that I switch to 2.86 anyway in forky.
So: No need to backport anything. Just point to your PR
in github. The change is very simple anyway so it's
trivial to backport in either case.
Thanks.
