ksh.ppc64le: I: -- SLE Conflict -- File: /bin/ksh Linkto: /etc/alternatives/ksh ksh.ppc64le: I: -- SLE Conflict -- File: /bin/ksh Linkto: /etc/alternatives/ksh ksh.ppc64le: I: -- SLE Conflict -- File: /etc/alternatives/ksh ksh.ppc64le: I: -- SLE Conflict -- File: /etc/alternatives/ksh.1.gz ksh.ppc64le: I: -- SLE Conflict -- File: /etc/alternatives/usr-bin-ksh ksh.ppc64le: I: -- SLE Conflict -- File: /usr/bin/ksh Linkto: /etc/alternatives/usr-bin-ksh ksh.ppc64le: I: -- SLE Conflict -- File: /usr/bin/ksh Linkto: /etc/alternatives/usr-bin-ksh ksh.ppc64le: I: -- SLE Conflict -- File: /usr/share/man/man1/ksh.1.gz Linkto: /etc/alternatives/ksh.1.gz ksh.ppc64le: I: SUSE_Backports_policy_ignored-SLE_alternatives_conflict mksh: /bin/ksh mksh: /etc/alternatives/ksh mksh: /etc/alternatives/ksh.1.gz mksh: /etc/alternatives/usr-bin-ksh mksh: /usr/bin/ksh mksh: /usr/share/man/man1/ksh.1.gz This package conflicts with files provided by SLE via the 'alternatives' system and they are whitelisted to be allowed in the Backports project. ksh.src:393: W: macro-in-comment %{libdir} ksh.src:394: W: macro-in-comment %{libdir} ksh.src:395: W: macro-in-comment %{libdir} There is a unescaped macro after a shell style comment in the specfile. Macros are expanded everywhere, so check if it can cause a problem in this case and escape the macro with another leading % if appropriate. ksh.ppc64le: W: missing-call-to-setgroups-before-setuid /lib64/ast/libast.so.5.4 ksh.ppc64le: W: missing-call-to-setgroups-before-setuid /lib64/ast/libshell.so.1.1 This executable is calling setuid and setgid without setgroups or initgroups. There is a high probability this means it didn't relinquish all groups, and this would be a potential security issue to be fixed. Seek POS36-C on the web for details about the problem. ksh-devel.ppc64le: W: no-version-in-last-changelog ksh.ppc64le: W: no-version-in-last-changelog ksh.src: W: no-version-in-last-changelog The latest changelog entry doesn't contain a version. Please insert the version that is coherent with the version of the package and rebuild it. 3 packages and 0 specfiles checked; 0 errors, 8 warnings.