[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1058704: marked as done (ITP: nsncd -- Name service non-caching daemon)



Your message dated Fri, 22 Dec 2023 19:00:31 +0000
with message-id <E1rGkl5-00FV9E-51@fasolo.debian.org>
and subject line Bug#1058704: fixed in nsncd 1.4.1-1
has caused the Debian Bug report #1058704,
regarding ITP: nsncd -- Name service non-caching daemon
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 owner@bugs.debian.org
immediately.)


-- 
1058704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058704
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Philipp Kern <pkern@debian.org>
X-Debbugs-Cc: debian-devel@lists.debian.org, pkern@debian.org

* Package name    : nsncd
  Version         : 1.4.1 (plus patches[1])
* URL             : https://github.com/twosigma/nsncd
* License         : Apache 2.0
  Programming Lang: Rust
  Description     : Name service non-caching daemon

 nsncd implements the NSCD (name-service caching daemon) protocol to
 provide out-of-process NSS lookups but does not implement caching.

 It is designed to provide high-performance NSS lookups for programs
 that are not using the system libc, while providing semantics as if
 NSCD were not being used.

This is useful in environments in which you are mixing binaries from
several sources. One such environment is Nix, where binaries will
be linked to a (hermetic) glibc from the Nix store. By dropping the
need to cache, nsncd is a lot simpler than nscd - it's only purpose
is to decouple your binaries from the NSS modules you have configured,
which will continue to run under the system glibc.

I'm going to maintain the package for the time being. If the Rust team
also wants to maintain Rust leaf software, I'm also happy to collaborate
there.

Kind regards
Philipp Kern

[1] The Nix people also added support for host resolution in
    https://github.com/nix-community/nsncd/.

--- End Message ---
--- Begin Message ---
Source: nsncd
Source-Version: 1.4.1-1
Done: Philipp Kern <pkern@debian.org>

We believe that the bug you reported is fixed in the latest version of
nsncd, 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 1058704@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Kern <pkern@debian.org> (supplier of updated nsncd 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 22 Dec 2023 11:39:41 +0100
Binary: nsncd nsncd-dbgsym
Source: nsncd
Built-For-Profiles: noudeb
Architecture: amd64 source
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Philipp Kern <pkern@debian.org>
Changed-By: Philipp Kern <pkern@debian.org>
Closes: 1058704
Description:
 nsncd      - Name service non-caching daemon
Changes:
 nsncd (1.4.1-1) unstable; urgency=medium
 .
   * Upload to Debian proper. (Closes: #1058704)
   * Make the package a proper Debian source package of version 3.0 (quilt).
   * Make the package build with Debian-native build-dependencies and tooling
   * Move nsncd from /usr/lib to /usr/libexec; it is not intended to
     be run manually by users.
   * Add a /etc/default/nsncd configuration file that is being read by
     the systemd service.
Multidist: yes
Checksums-Sha1:
 c96c705c03352bb528e0688ebc7b64a3431a0a45 1926 nsncd_1.4.1-1.dsc
 f6f431c7170c7dfce44cfaf91538e60090d1ebf8 4804 nsncd_1.4.1-1.debian.tar.xz
 f2a48308a18236e8ed78d411fe21db5022abcf01 4244684 nsncd-dbgsym_1.4.1-1_amd64.deb
 0a80a36e901bffe807d67144adfe00cff31c0e9a 13982 nsncd_1.4.1-1_amd64.buildinfo
 eed8532e48cdbd0d1a1df353d3ec2a06c4cc48eb 309364 nsncd_1.4.1-1_amd64.deb
 572066eab783ee3201da0cf7658fceb5b9399ed2 61856 nsncd_1.4.1.orig.tar.xz
Checksums-Sha256:
 bc931d72d58a5744b8117bb4f8cd6c3b03205850919d0fa54e4f9cfa7933f7e1 1926 nsncd_1.4.1-1.dsc
 36e5559953716040b11dc322ec09811f8432ef23ac8e181e7cada79a951f58e6 4804 nsncd_1.4.1-1.debian.tar.xz
 1311d8f8d855bbd2313711e3d44c477a884f29c445a8f447c4f92a2da86c18d7 4244684 nsncd-dbgsym_1.4.1-1_amd64.deb
 1c2568560ffadc353cf5a6c9f871fe8ba6e4e707f95a776fd2c3a2e983408f02 13982 nsncd_1.4.1-1_amd64.buildinfo
 56c58b6428f9418b21f81c417cfd0dbfc11a2101f0ba6e773449dc162e4ddc02 309364 nsncd_1.4.1-1_amd64.deb
 3df9244b1583fa843f38200ecb539270a145ac218244b078295be1558926bbb8 61856 nsncd_1.4.1.orig.tar.xz
Files:
 655912675882af7b408bafafc8752b3b 1926 misc optional nsncd_1.4.1-1.dsc
 5f647d34777c5f5c156cb4c947c43721 4804 misc optional nsncd_1.4.1-1.debian.tar.xz
 072e67c9cdd6d80f800a79877ad9e3c0 4244684 debug optional nsncd-dbgsym_1.4.1-1_amd64.deb
 99654f6bbd56c653395706a3244284bc 13982 misc optional nsncd_1.4.1-1_amd64.buildinfo
 000e499d0eb09559f3ad51d707734821 309364 misc optional nsncd_1.4.1-1_amd64.deb
 c98b0248be903294162f4cd79abffeae 61856 misc optional nsncd_1.4.1.orig.tar.xz

-----BEGIN PGP SIGNATURE-----

iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAmWFd88RHHBrZXJuQGRl
Ymlhbi5vcmcACgkQRG4lRTXQVuxIFQf9G80svFgRc5aXCDfXvmOo9rrWXCzsnJNP
b+xZ1vySJfewvFXHjA/SKsVpP86ZkaVerx9Lg27FQ8yJsfJPPVMfpmlv9CicpC6c
NOMoiItyQxly7n1sRBiLUI3dikAKU4ZCchQRnO5ZfrKNGjD8jyFERqiUzeub0RGv
jA1nhNuwVthotDgLQ1hWovqLNRAsj+ERhveUuC5VFsXIIPb97Zbd0cCXEhafpjkG
X6mkmP7pkvt6ruTdJy1LrcIxNXiGyV30/STrjRpwphvSm+bKWm+8sp89rhkIkECR
OTKAUGVpZMajc21a+XxtU01a1Tihcwa20CB8UyGSq51pey7S4yDEuA==
=98Am
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: