Source: libasyncns
Version: 0.8-6
Severity: important
X-Debbugs-Cc: Tanguy Ortolo <tanguy+deb...@ortolo.eu>, Tanguy Ortolo
<tan...@debian.org>, debian-devel@lists.debian.org, 862...@bugs.debian.org,
862...@bugs.debian.org, Package Salvaging Team <team+salv...@tracker.debian.org>
Hi Tanguy,
Your package libasyncns was highlighted in the Bug of the Day[1]
initiative, which aims to introduce newcomers to manageable tasks and
guide them through the workflow to solve them. The focus of this
initiative is on migrating packages to Salsa, as it's a great way to
familiarize newcomers with a consistent Git-based workflow.
First of all, thank you for your past work on the Debian package
libasyncns. According to popcon[2], usage of the package is not only
steady but even increasing, which is quite remarkable for software that
has not seen an upstream release in some time.
I noticed that the Debian package was last uploaded in 2016, and
although it has no open release-critical bugs, two bugs were reported in
2017, both with patches attached. These patches were also forwarded
upstream, but given upstream appears inactive, Debian may now be the
primary place where users can expect fixes.
Since I haven't seen any uploads from you since 2018 and there hasn't
been a response to these bug reports, I wanted to kindly ask whether you
are still interested in maintaining this package. I fully understand
that priorities and availability change over time — especially for
volunteer work — and I don’t want to assume anything. I just want to
clarify how we might ensure the package continues to get the attention
it needs.
As is common practice in the Bug of the Day initiative, I created a Git
repository on Salsa[3] to demonstrate how the package could be
modernised and the existing bugs addressed. I’ve included the suggested
patches from the open bugs, though I’ve not added them in
debian/patches/series to allow for further review.
Please note: I do not consider this repository under the Salvage Team
namespace to be the final or rightful place for ongoing maintenance. If
the package continues to be maintained, I believe it should ideally move
either to your preferred location or perhaps under Debian team if that
seems appropriate. I'm happy to help move or remove the repository
depending on your wishes.
I’m also sending this message to debian-devel to raise awareness and
possibly find new contributors interested in the package. If you feel
that you no longer have the time or interest to maintain it, it might be
helpful to mark this bug as a Request for Adoption (RFA) by retitling it
accordingly. That would make the situation clearer and help with the
search for a new maintainer. Alternatively, if you’re fine with someone
doing a QA upload[4], that could also be a practical next step.
If you are still interested in maintaining it, that’s great — and if
you’d prefer to hand it over or co-maintain it, I’d be happy to help
find someone willing to assist.
Many thanks again for your past efforts, and looking forward to your
thoughts.
Kind regards
Andreas.
[1] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
[2]
https://qa.debian.org/popcon-graph.php?packages=libasyncns0&show_installed=on&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
[3] https://salsa.debian.org/salvage-team/libasyncns
[4]
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#nmus-vs-qa-uploads
-- System Information:
Debian Release: 13.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
