$ dnf repoquery --repo=rawhide --requires glusterfs-geo-replication | grep python /usr/bin/python2 python3 python3-gluster = 5.0-0.1.rc0.fc30 python3-prettytable Is this desirable? It's shebangs: $ rg python2 usr/libexec/glusterfs/peer_mountbroker.py 1:#!/usr/bin/python2 usr/libexec/glusterfs/peer_mountbroker 1:#!/usr/bin/python2 usr/libexec/glusterfs/peer_georep-sshkey.py 1:#!/usr/bin/python2 usr/libexec/glusterfs/gfind_missing_files/gfid_to_path.py 1:#!/usr/bin/python2 usr/share/glusterfs/scripts/schedule_georep.py 1:#!/usr/bin/python2 usr/libexec/glusterfs/python/syncdaemon/conf.py 1:#!/usr/bin/python2 usr/libexec/glusterfs/python/syncdaemon/changelogagent.py 1:#!/usr/bin/python2 usr/libexec/glusterfs/python/syncdaemon/gsyncd.py 1:#!/usr/bin/python2 usr/libexec/glusterfs/python/syncdaemon/gsyncdstatus.py 1:#!/usr/bin/python2 Happens on: glusterfs-geo-replication-0:5.0-0.1.rc0.fc30 glusterfs-geo-replication-0:5.0-0.2.rc0.fc30
It's probably because there's no /usr/bin/python3 in the mock job that creates the SRPM, so the shebangs get wacked from python3 to python2 by BuildSRPM job.
Just curious. What part of BuildSRPM changes shebangs?