On 7/12/24 04:01, Andrej Shadura wrote:
Hello,
On Fri, 12 Jul 2024, at 03:25, Andrew Palardy wrote:
I'm also impacted by this bug. I'd like to resolve it (patch below).
However, the ownership of this package is uncertain.
There is no maintained upstream for Tayga. It's origin hasn't
published since 2011, long before RFC8215 was published. This bug
impacts more than Debian, and I'm not sure which team would be best
to take this on (Debian, FreeBSD, ... are all impacted by this).
Does the Debian community have any advice for how to take ownership
of this package in a way that doesn't involve sending separate
patches to the versions being maintained by each distro independently?
Thank you for the patch, I’ll have a look at it later. I think it
would be fair to ask the upstream author (cc’d) about his intentions
and plans about the project.
Hi all,
Thanks for getting in touch. I took a 10+ year break from programming to
have kids and work at a few cocktail bars, but I'm getting back into
software again.
In addition to your email I also recently heard from a government agency
that they might be forced to stop using Tayga because it appears to be
unmaintained, so there is some urgency coming from multiple directions.
I have a couple vacations coming over the next six weeks, but I'll try
to convert the existing Mercurial repo to Git and set up a project on
GitHub before I leave, and then spend some time on a new release this
fall. -Nathan
