(In reply to Max Lin from comment #2) > Those are from busybox-links, I did fighting with busybox-sysvinit-tools vs. > sysvinit-tools issue within the latest snapshot, I did realize we should > blacklist those package in NON_FTP_PACKAGES.group, however I'm surprised TW > ship those binaries... how did TW avoid this busybox-foo issue? I know where the package comes from. My question is whether it has already been installed before this conflict occurs. If it has been, then zypper can probably do nothing here, but if it hasn't, then zypper shouldn't have picked the busybox package in the first place.