Mailinglist Archive: opensuse-factory (607 mails)

< Previous Next >
Re: [opensuse-factory] New Tumbleweed snapshot 20200220 released! - hanging update of an older system!
* Jiri Slaby <jslaby@xxxxxxx>, le 24-02-20, a écrit:
On 24. 02. 20, 6:50, Thorsten Kukuk wrote:
On Sun, Feb 23, Andrei Borzenkov wrote:

No. What is being stubbornly ignored here - no user who reported this
problem did consciously modify this file.

Which is wrong. RPM is checking the checksum of that file, and the checksum
is not lying. This users did modify this file, maybe not implicit, but
then by using YaST and making changes to it. Like configuring NIS.

It's actually not that wrong. It's not only configuring NIS. And even if
it were, it doesn't matter, people shouldn't care about changed
underlying files at all.

If you don't exactly know what you are doing does not mean that you are
not doing it.

That is what "consciously" means in the above sentence, IMO.

Looking at the nth report of the same, whoever introduced this state,
should fix it. No matter how /etc/nsswitch.conf was modified, an update
shall not break a working system. Period. If it does, _we_ failed, not
them. And if we keep repeating "you did update the file, handle it", we
are only losing users, right?

/me neither changed /etc/nsswitch.conf manually and I had to fix this
mess up. If yast or some %post script did it, OK, so what -- should I
fix it? Not at all, the update should as I am using high-level tools
like yast. If we are to modify files anyway, we can drop yast completely
as it becomes useless.

If this is not resolved properly, I vote for reverting the change in
Tumbleweed, so that it does not propagate any further. Especially to Leap.

In support:

I do not know whether this excerpt of a former mail can help but my original
/etc/nsswitch.conf was modified, the initial version being renamed

Here is the change, which added "mdns_minimal [NOTFOUND=return]" on line 29

# diff nsswitch.conf nsswitch.confbak
< hosts: files mdns_minimal [NOTFOUND=return] dns
hosts: files dns

I may have caused it unwittingly, but I never knew it had occured until now,
and I still do not know what caused it. Actually I did not even know what it
meant until I searched yesterday. And now that I know, I still wonder what it
is useful for.

Then how am I to know how to operate the merge between /etc/nsswitch.conf and
nsswitch.conf.rpmnew ?

Tools that edit configuration files should leave comments so that users do not
have to make choices they do not understand.



Bernard.Lang@xxxxxxxxxx ,_ /\o \o/ mobile +33 6 6206 1693 ^^^^^^^^^^^^^^^^^ fixe +33 1 3056 1693

To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups