Description of problem: systemtap binaries in /usr/bin/stap{,-prep,-report} are provided by both systemtap-client and systemtap-devel. This is probably a packaging bug, found while reviewing file duplication between packages---it turns out it's the only such duplicate (other than 'alternatives'-handled /usr/bin/mailq) Version-Release number of selected component (if applicable) systemtap-client-3.1-2.fc25.x86_64 systemtap-devel-3.1-2.fc25.x86_64 How reproducible: very Steps to Reproduce: 1. rpm -qf /usr/bin/stab Actual results: systemtap-devel-3.1-2.fc25.x86_64 systemtap-client-3.1-2.fc25.x86_64 Expected results: systemtap-client-3.1-2.fc25.x86_64
Thanks for your report. It turns out that this is a deliberate decision. As outlined within the .spec file, the -devel subrpm is for building systemtap modules (running pass 1..4); the -client subrpm is for being able to build systemtap modules -remotely-. Both those tasks happen to be performed by the same binary.