Comment # 8 on bug 911756 from Wolfgang Bauer

(In reply to Cor Blom from comment #7)
> Still strange that it only surfaces now.

Well, at least I did get those conflict warnings immediately after upgrading to
13.2 already when running "zypper ve". But I ignored them upto now.

For the upgrade to 13.2 I used 13.1's zypper (I upgraded via "zypper dup")
which did not check for file conflicts yet.

So at least in my case, this is perfectly explainable... ;)

I don't know about the reporter, but maybe he upgraded to Tumbleweed from 13.1
just recently or something like that?