On Wed, May 23, 2018 at 6:24 PM, Miro HronĨok <mhroncok(a)redhat.com> wrote:
How exactly is this change breaking users' software? We certainly
want to
avoid that.
If anything installed from outside our repos calls `/usr/bin/python`,
we break it. Unless we install the new python symlink package
alongside, but if we're doing that automatically, then how are we
testing the change? Maybe that is the intent, and I just
misunderstood.
How does that force the maintainers to fix the packages? We tried to
check
what packages use /usr/bin/python during build. There is a huge warning in
the build log and a failed Taskotron check if the package uses it. Nobody
(or close to nobody) cared.
If we test it against a symlink-less python2 package, we have a list
we can file bugs against. From that point, we can become increasingly
annoying to package maintainers.