http://bugzilla.opensuse.org/show_bug.cgi?id=1106839
http://bugzilla.opensuse.org/show_bug.cgi?id=1106839#c3
Michael Andres
Other users reported no conflict for their updates. What I did differently, is I updated "zypper" separately before updating everything else. So I might have been using a newer "zypper" than the people who did not see conflict messages.
I think it's the calibre package which 'fools' the file conflict check. Probably related to bug #1104597. The file conflict check is run before the package installation actually starts and it takes the situation on disk into account. It looks like older calibre packages actually created a symlink
/usr/share/calibre/fonts/liberation -> /usr/share/fonts/truetype
So the check sees /usr/share/calibre/fonts/liberation/LiberationMono-Bold.ttf and /usr/share/fonts/truetype/LiberationMono-Bold.ttf denoting the same location on disk (i.e. possibly a file conflict). Newer calibre packages however, manually remove those symlinks in their pretrans scripts
pretrans scriptlet (using <lua>): path = "/usr/share/calibre/fonts/liberation" st = posix.stat(path) if st and st.type == "link" then os.remove(path) end ...
That's why the locations are not overwritten, but this is something the file conflict check can't see. So whether you see this apparently bogus conflict depends on which calibre version is actually installed (the symlink still present on disk or not). -- You are receiving this mail because: You are on the CC list for the bug.