Your message dated Thu, 12 Jan 2017 23:04:17 +0000
with message-id <e1cropp-0007g2...@fasolo.debian.org>
and subject line Bug#851180: fixed in nss-mdns 0.10-8
has caused the Debian Bug report #851180,
regarding Installing libnss-resolve before libnss-mdns breaks mDNS name 
resolution
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 ow...@bugs.debian.org
immediately.)


-- 
851180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnss-resolve
Version: 232-6
Severity: serious
Justification: Breaks another package

Hi!

A freshly installed Debian Stretch system will have a
/etc/nsswitch.conf like this (see libc-bin's postinst and/or
/usr/share/libc-bin/nsswitch.conf):

        # /etc/nsswitch.conf
        #
        # Example configuration of GNU Name Service Switch functionality.
        # If you have the `glibc-doc-reference' and `info' packages installed, 
try:
        # `info libc "Name Service Switch"' for information about this file.

        passwd:         compat
        group:          compat
        shadow:         compat
        gshadow:        files

        hosts:          files dns
        networks:       files

        protocols:      db files
        services:       db files
        ethers:         db files
        rpc:            db files

        netgroup:       nis

Installing libnss-resolve makes these changes:

        --- nsswitch.conf       2016-12-04 15:16:42.701978711 +0100
        +++ /etc/nsswitch.conf  2016-12-04 15:16:51.965961200
+0100
        @@ -9,7 +9,7 @@
         shadow:         compat
         gshadow:        files
         
        -hosts:          files dns
        +hosts:          files resolve [!UNAVAIL=return] dns
         networks:       files
         
         protocols:      db files

If the user then installs for example the "gnome" meta package, 
libnss-mdns and libnss-myhostname will be installed as well because of
these dependencies/recommendations: 

        gnome -> avahi-daemon -> libnss-mdns
        gnome -> gnome-core -> gnome-control-center -> libnss-myhostname

This results in the following hosts line:

        hosts:          files resolve [!UNAVAIL=return] mdns4_minimal 
[NOTFOUND=return] dns myhostname

However, because of the "[!UNAVAIL=return]" introduced with [0],
nothing after "resolve" will actually be tried. This is mostly
harmless, since "resolve" provides a superset of "dns" and
"myhostname", but it breaks mDNS as resolved currently does not resolve
mDNS names like "foo.local".

Please note, that

 a) This bug depends on the order of package installations. Installing 
    libnss-resolve *AFTER* everything else will avoid the problem.
 b) I think the rationale for the change made in [0] is sound, so
    simply reverting the change is not a solution.

IMHO the best solution would be to

 a) Activate the mDNS support in resolved [1] if possible.
 b) Talk to the GNOME/Avahi maintainers and make them recommend libnss-
    resolve instead of the others
 c) Eventually remove libnss-mdns and libnss-myhostname from Debian
    as both aren't really maintained anymore and have been superseded
    by libnss-resolve.

Best regard

Alexander Kurtz

[0] 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=5e0095416366eb86590d6e31242097ded5201b3a
[1] https://github.com/systemd/systemd/blob/master/src/resolve/resolved-mdns.c

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
Source: nss-mdns
Source-Version: 0.10-8

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

Debian distribution maintenance software
pp.
Simon McVittie <s...@debian.org> (supplier of updated nss-mdns 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 12 Jan 2017 22:11:47 +0000
Source: nss-mdns
Binary: libnss-mdns
Architecture: source
Version: 0.10-8
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Simon McVittie <s...@debian.org>
Description:
 libnss-mdns - NSS module for Multicast DNS name resolution
Closes: 500478 782281 782282 851180
Changes:
 nss-mdns (0.10-8) unstable; urgency=medium
 .
   * debian/gbp.conf: use DEP-14 branch names (debian/master and
     upstream/latest)
   * Standards-Version: 3.9.8 (no changes needed)
   * libnss-mdns.postinst: remove special code to handle upgrades from
     ancient versions (all were older than squeeze)
   * libnss-mdns.postinst: configure libnss-mdns before libnss-resolve
     (mitigates: #846944, Closes: #851180)
   * libnss-mdns.postinst: shuffle libnss-mdns before libnss-resolve
     during upgrade if necessary
   * debian/tests: add autopkgtests for the interaction between
     libnss-mdns and libnss-resolve
   * debian/rules: enable bindnow hardening
   * Bump debhelper compat level to 10
     - do not explicitly use autoreconf, it is now the default
   * debian/rules: FTBFS if files are built but not installed
   * libnss-mdns.postrm: do not deconfigure the module until the
     package is purged (Closes: #500478, #782281, #782282)
     - debian/tests/nss-behaviour: verify that the glibc < 2.11 bug
       that caused #534304 has been fixed, so leaving unavailable
       NSS modules in /etc/nsswitch.conf is harmless
     - debian/tests: add autopkgtests for #500478, #782281, #782282
Checksums-Sha1:
 fd262c706e8061590989d7bddfd1cb5cbec865b9 2071 nss-mdns_0.10-8.dsc
 22a6cfd9c73d405cdbbd6dcbedaf48e498b8bbdb 11996 nss-mdns_0.10-8.debian.tar.xz
Checksums-Sha256:
 37db38a5d6fbb6b13da34fdaf38b9f68f8464c139dd3c4aa0ee5529b45e6adf5 2071 
nss-mdns_0.10-8.dsc
 1ae0914b48a3bd4f1d4c6c69e5fa7594529f54451ae6cc02abdcbeb70a3a36ff 11996 
nss-mdns_0.10-8.debian.tar.xz
Files:
 5b0ea4eccc1f5f9b62a9d5439e5bb860 2071 admin optional nss-mdns_0.10-8.dsc
 bc17a13a00eebae8a0aaa656bf59446c 11996 admin optional 
nss-mdns_0.10-8.debian.tar.xz

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

iQIzBAEBCAAdFiEE2pjyXAhxxJpZ6v8sTej/KmPHzJAFAlh4BWoACgkQTej/KmPH
zJBEHA//RklH1UcyHFbG1sbGMgncjlfQGeUFHurdvmMNP40Ls6uplI+GykkguwZg
Fd++oboI5Uzw+aagkof3MAs5xEEJ2YHPuU0LNgSOoyJUbKzOwdtfO1REGwH4ns/3
AWoebyIaUEZND3WSeletnHkTdyG0RwrJh/6PM7xjsDMCPjEStteqCYgBg8txY97n
7AehcQNN4hq3C7czXYKZR0KNpfFB3c++3PR5j0CY3IS60TRSoK2Wpmpc5gykAdEx
ctfP+3yeJpGZVZe0rqAdX4CyVNMx5EmkocBP7iLD/fMVQBdacdlHoYNDMuXzycZI
ZVMQNOgOjmd9dMK3xChsWdby99ZPtnucr32DbZINNMfWTvTu1gilHBGaBdwpo+Wv
vHMJtafJ5HZXsdVeQWWlP91bc/TrWW5bEd9af0aJULLIOdvZswwLKC41BsyrWkey
GqSgMBRIUYWKxWwQ/cm3vrjw8xofzgSdCW4pSGqdpgEz2omA750eiK1IyP5WnHW7
re0DbcE6h19dbeoGYLY9wyS4zvgbNzZjRZZNcZjA3PGa1dFb/pz5OP7WHQKtU7nL
P8XJtaThH6BDxJUCertaBew1xoZtVEd/IasVexjvDvmqoO68vzlITX+3HHZqzvMX
lto019piB6H6d/rSQ9d/mCSn/WUSxBXXrEIxrSweERGkUmhWOgI=
=BNZl
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to