Your message dated Fri, 05 Sep 2025 06:50:49 +0000
with message-id <[email protected]>
and subject line Bug#1107475: fixed in libasyncns 0.8-7
has caused the Debian Bug report #1107475,
regarding libasyncns: Intend to Orphan
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1107475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107475
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libasyncns
Version: 0.8-6
Severity: important
X-Debbugs-Cc: Tanguy Ortolo <[email protected]>, Tanguy Ortolo
<[email protected]>, [email protected], [email protected],
[email protected], Package Salvaging Team <[email protected]>
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
--- End Message ---
--- Begin Message ---
Source: libasyncns
Source-Version: 0.8-7
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libasyncns, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <[email protected]> (supplier of updated libasyncns package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 20 Aug 2025 13:59:26 +0200
Source: libasyncns
Architecture: source
Version: 0.8-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1107475
Changes:
libasyncns (0.8-7) unstable; urgency=medium
.
* QA upload.
Closes: #1107475
* Maintain package in Debian/ team space on Salsa
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Secure URI in copyright format (routine-update)
* Trim trailing whitespace.
* Use secure URI in Homepage field.
* Avoid explicitly specifying -Wl,--as-needed linker flag.
* watch file standard 4 (routine-update)
* Enable dh_missing --fail-missing which is default in compat level 13
* Drop unused lintian-override
* d/copyright: Drop unneeded/outdated paragraph
Checksums-Sha1:
568346184fb1cc59564412d9c6f69823f42d7f5e 1949 libasyncns_0.8-7.dsc
43e16ca16c3693e9791f0ab59ce6fbbfe5f7764c 5152 libasyncns_0.8-7.debian.tar.xz
104060be2ebf9657d9eba56136d49d8922b2bf50 6590 libasyncns_0.8-7_amd64.buildinfo
Checksums-Sha256:
c1deb7b591ef55e92a5a17b998bd7e2108d41e21ab0d86da95598f3a57144007 1949
libasyncns_0.8-7.dsc
238cf611711cfd4f9a90fff178e01cc2406516ffb856caaac6b0f7a0c605cf6b 5152
libasyncns_0.8-7.debian.tar.xz
862a48f6c67d302aa0e427f60bc0d72eb36afe55e789a906b1d96c3740444212 6590
libasyncns_0.8-7_amd64.buildinfo
Files:
13dd04d91c0f8f61664a8da76d533e61 1949 libs optional libasyncns_0.8-7.dsc
19a0fd3c711c9679e6c8a5aca4e6e110 5152 libs optional
libasyncns_0.8-7.debian.tar.xz
508f48952f224a264b0e5421e3df526a 6590 libs optional
libasyncns_0.8-7_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmimtFURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHwyQ//dJGN8uQJe5FhVgZ9bUmvnuMWIolkSTaP
eJWDf5yNeirg23r9IugkOSSFNalbL9ePG2ARA87SjtaRgO6XFfTUuRhjLTCcSIIU
E5DE6Xro8dF3ByuSBkxUpAi0o95H//aY08N0Az4CDTvbhN3KDrCOKJVsScoxa8iY
tUDLY9swl3lncUKZJC/MZIyX1scN4QYCx/vWepYE9O1aAE7qk1UQWdUJDctN3/r5
Cjf/s2IqVsWu6ZC7QbFEykraWHFVK1ob86+k9S+ew1fvdEP4QUvknpyPw5+uqIy7
ojvShlUZdDLD+Zuy+8HH88yaeg+6Q3IhoicTZISOtwoWlKJgutqAX7jXwikYNPOy
Ypi9le63Ehk2EgvTgWs4RclWCErx5TPnCTexd66ZvI6wsktFFeZjzW5M6WXUH4Cj
QdVZc4zS/5jxDF19+K8gH4OnLQ27V3czLGHLdZ3SOtsLmQ5WOtC8knTz5kd+tVEJ
Sez3yN5KQdUMl0QhIkIvRR5H+IEzcJbn8ALzmO5FUmwjW0gKik0YAVUz4SEmtXDU
4AcHFL5kW2FyXkAlXIkWJBhdVGnhGtOmWYcZO3Utk4G9nwe2k8wFknsPVSMCrHIz
4wub9kWkZ8I/x5+Tw/rGVv+BnjnQ10aMbCD9NYzz8u6DSS8tpBEgEM3XGEGgkrcY
2JfvWtjYnLw=
=pMvd
-----END PGP SIGNATURE-----
pgpmwlkCSMv3m.pgp
Description: PGP signature
--- End Message ---
