https://bugzilla.suse.com/show_bug.cgi?id=1180689 https://bugzilla.suse.com/show_bug.cgi?id=1180689#c2 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Other Assignee|yast2-maintainers@suse.de |max@suse.com QA Contact|jsrain@suse.com |qa-bugs@suse.de --- Comment #2 from Thorsten Kukuk <kukuk@suse.com> --- 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. My guess is adding: Supplements: packageand(chrony:branding-openSUSE) to chrony-pool-openSUSE and packageand(chrony:branding-SLE) to chrony-pool-SUSE would fix this. -- You are receiving this mail because: You are on the CC list for the bug.