Bug#1025372: RFS: nss-tls/1.1-1.1 [NMU] -- utility like nslookup(1), but uses libnss_tls.so instead of DNS

[Gioele Barabucci]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for a NMU of the package "nss-tls":

* Package name : nss-tls
Version : 1.1-1.1
Upstream contact : Dima Krasner <di...@dimakrasner.com>
* URL : https://github.com/dimkr/nss-tls
* License : LGPL-2.1+
* Vcs : https://salsa.debian.org/debian/nss-tls
Section : net

The source builds the following binary packages:

nss-tlsd - encrypted DNS name resolution daemon
libnss-tls - NSS module for encrypted DNS name resolution
tlslookup - utility like nslookup(1), but uses libnss_tls.so instead
of DNS

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/nss-tls/

Alternatively, you can download the package with 'dget' using this command:

dget -x
https://mentors.debian.net/debian/pool/main/n/nss-tls/nss-tls_1.1-1.1.dsc

Changes since the last upload:

nss-tls (1.1-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* d/libnss-tls.nss: Install NSS service `tls` via dh_installnss
(Closes: #1024688)

Regards,

--
Gioele Barabucci

[Adam Borowski]

On Sat, Dec 03, 2022 at 11:53:23AM +0100, Gioele Barabucci wrote:
> I am looking for a sponsor for a NMU of the package "nss-tls":

> nss-tls (1.1-1.1) unstable; urgency=medium
> .
> * Non-maintainer upload.
> * d/libnss-tls.nss: Install NSS service `tls` via dh_installnss
> (Closes: #1024688)

Hi!
Could you please follow the NMU procedure? This is not a high-severity or
urgent bug, thus I see no reason to skip the rules.

The Policy has details, but in short: please post to a bug (in this case
#1024688) that you intend to do a NMU, adding a debdiff of the proposed
changes (in this case, the Salsa merge request should be enough).

Only then the clock starts ticking, which is 10 days for regular NMUs.
Of course, if you believe the maintainer won't react, uploading to
DELAYED/10 (which in this case is done by a sponsor) will fulfill this
requirement while not requiring you to remember to do an action in the
future. But in either case, the intent-to-NMU mail is still required.


Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Quis trollabit ipsos trollos?
⠈⠳⣄⠀⠀⠀⠀

[Gioele Barabucci]

On 08/12/22 15:51, Adam Borowski wrote:
> On Sat, Dec 03, 2022 at 11:53:23AM +0100, Gioele Barabucci wrote:
>> I am looking for a sponsor for a NMU of the package "nss-tls":
>
>> nss-tls (1.1-1.1) unstable; urgency=medium
>> .
>> * Non-maintainer upload.
>> * d/libnss-tls.nss: Install NSS service `tls` via dh_installnss
>> (Closes: #1024688)
>
> Hi!
> Could you please follow the NMU procedure? This is not a high-severity or
> urgent bug, thus I see no reason to skip the rules.
>
> The Policy has details, but in short: please post to a bug (in this case
> #1024688) that you intend to do a NMU, adding a debdiff of the proposed
> changes (in this case, the Salsa merge request should be enough).

Hi, I haven't found a codified procedure in the policy nor in the
devref. I suppose it's one of those things one learns by doing. :)

Thanks for the guidance, the intent-to-NMU email has now been sent:

https://bugs.debian.org/1024688#10

--
Gioele Barabucci

[Gioele Barabucci]

On 09/12/22 12:35, Gioele Barabucci wrote:
> On 08/12/22 15:51, Adam Borowski wrote:
>> On Sat, Dec 03, 2022 at 11:53:23AM +0100, Gioele Barabucci wrote:
>>> I am looking for a sponsor for a NMU of the package "nss-tls":
>>
>>>   nss-tls (1.1-1.1) unstable; urgency=medium
>>>   .
>>>     * Non-maintainer upload.
>>>     * d/libnss-tls.nss: Install NSS service `tls` via dh_installnss
>>>       (Closes: #1024688)
>>

>> The Policy has details, but in short: please post to a bug (in this case
>> #1024688) that you intend to do a NMU, adding a debdiff of the proposed
>> changes (in this case, the Salsa merge request should be enough).
>

> [...]

>
> Thanks for the guidance, the intent-to-NMU email has now been sent:
>
> https://bugs.debian.org/1024688#10

Hi,

the intent-to-NMU email has not received any feedback after 20 days.

Regards,

--
Gioele Barabucci