https://bugzilla.suse.com/show_bug.cgi?id=1180689 https://bugzilla.suse.com/show_bug.cgi?id=1180689#c4 --- Comment #4 from Reinhard Max <max@suse.com> --- (In reply to Thorsten Kukuk from comment #2)
I guess more a packaging bug:
| chrony-pool-empty | Empty pool preconfiguration for chrony | package i | chrony-pool-openSUSE | Chrony preconfiguration for openSUSE | package | chrony-pool-suse | Chrony preconfiguration for SUSE | package
We have three chrony pool packages, and zypper uses the wrong one. There are ways to tell zypper which chrony-pool-* to prefer depending on the product/release package/branding. Seems this is missing.
It is a bug in the package selection for the respective products. When I was forced to introduce these preconfiguration packages despite of the concerns I had, it was promised to me that it would be made sure that openSUSE and SLE would alsways only contain their respective pool package, but not the other one. That way it would be impossible that the wrong one gets installed. -- You are receiving this mail because: You are on the CC list for the bug.