That was exactly the case. So I just built python3 to make it happy!
Thanks Dan (and others)
On 2/6/16, 4:26 AM, "Linux on 390 Port on behalf of Dan Horák"
wrote:
>IIRC such Requires: are added automagically by rpmbuild after
>inspecting the shebang lines in executable scripts.
---
On Thu, 4 Feb 2016 18:31:12 +
Neale Ferguson wrote:
> I am building an RPM that uses python. For some reason the rpm build
> process determines that python3 is required by the package, despite no
> reference being made to python3 and everything being built by python2.7.
> Here’s the line from
On Thu, 4 Feb 2016, Mark Post wrote:
> Do you have /usr/bin/python3 on your system? If so, you'll
> likely have to remove it until after the build is finished.
> I've found that even building packages without RPM sometimes
> necessitates this because things like ./configure find
> packages that I
>>> On 2/4/2016 at 01:31 PM, Neale Ferguson wrote:
> I am building an RPM that uses python. For some reason the rpm build
> process determines that python3 is required by the package, despite no
> reference being made to python3 and everything being built by python2.7.
> Here*s the line from the
I am building an RPM that uses python. For some reason the rpm build
process determines that python3 is required by the package, despite no
reference being made to python3 and everything being built by python2.7.
Here’s the line from the build that rpm build prints:
Requires: /bin/bash /bin/sh /us
