Description of problem:
Noticed the error "/sbin/sln no file or directory found" (or something like that) from a post-install script during weekly dnf upgrade. The package was glibc or glibc-devel or glibc-langpak-en.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. dnf upgrade
This is a distribution-level problem. You need to figure out which scriptlet calls sln and clone this bug for the respective component.
I grepped all the spec files and redhat-lsb is the only thing that calls sln...
*** This bug has been marked as a duplicate of bug 1625584 ***