Bug#846944: Installing libnss-resolve before libnss-mdns breaks mDNS name resolution

[Michael Biebl]

Control: clone -1 -2
Control: reassign -2 libnss-mymachines
Control: found -2 222-3
Control: retitle -2 libnss-mymachines should be ordered before resolve


Am 13.01.2017 um 22:48 schrieb Felipe Sateler:
> On 13 January 2017 at 18:24, Michael Biebl <biebl at debian.org> wrote:
>>>>> libnss-mymachines - nss module to resolve hostnames for local container instances
>>>
>>> This is meant to be after files but before resolve (so the same position
>>> as libnss-docker and libnss-gw-name). Are you deliberately installing it with
>>> a lower priority than upstream's recommendation?
...

> This was the upstream recommendation at the time. That was changed in
> upstream commit 9053aaad4255a1d01a50f8e44784cd7eebe8f95c , with the
> following log message:
> 
>     man: change recommended order of NSS modules in /etc/nsswitch.conf
> 
>     So far we recommended placing "nss-mymachines" after "nss-resolve"
> in the order
>     of preference in /etc/nsswitch.conf. This change reverse this
> order.

..
> 
> So I guess we just failed to update usage with upstream?
> 

I think so. Let's clone this for libnss-mymachines to get this updated.

Felipe, do you want to look into this?

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170113/b9478c3b/attachment-0002.sig>