Bug 878409

Summary:	Need to reinstall nss-mdns after every glibc upgrade
Product:	[Fedora] Fedora	Reporter:	Bastien Nocera <bnocera>
Component:	nss-mdns	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	alvaropg, john.ellson, lpoetter, metanoite, rmarko, samtygier, tim
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-05 13:09:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bastien Nocera 2012-11-20 11:20:15 UTC

nss-mdns-0.10-11.fc18.x86_64
glibc-2.16-20.fc18.x86_64

Every upgrade causes /etc/nsswitch.conf to be overwritten. This is too fragile. glibc should have a .d/ directory where customisations could be made, or it should stop clobbering the /etc/nsswitch.conf file.

yum reinstall nss-mdns
re-runs the post install script and fixes the problem.

Finally, nss-mdns could use a trigger script to fix the problem every time glibc is updated:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s02.html

Comment 1 ZiN 2013-02-06 13:11:41 UTC

No, neither glibc nor nss-mdns should touch nsswitch.conf when upgrading, as its' configuration can be somewhat different from the default. For example, one can use mdns_minimal, while another - mdns_minimal4 or mdns_minimal6 etc.
Perhaps, it's better assign this bug to glibc.

Comment 2 Tim Niemueller 2013-05-07 11:12:27 UTC

Having the same issue everytime glibc is upgraded. I agree that this should be re-assigned to glibc.

Comment 3 John Ellson 2013-05-09 16:54:43 UTC

See also: #867124

Seems to me that zeroconf should be considered default.  Whats the point of zeroconf if you have to configure it!

Comment 4 Álvaro Peña 2013-05-13 08:31:57 UTC

Same error with nss-myhostname package.

Comment 5 Fedora End Of Life 2013-12-21 09:26:54 UTC

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2014-02-05 13:09:52 UTC

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.