On Sunday, February 4, 2018 2:29:26 PM EST Alec Leamas wrote: > On 04/02/18 19:30, Steve Grubb wrote: > > On Sunday, February 4, 2018 12:42:56 PM EST Antonio Trande wrote: > > > >> Not enough information to check signature validity. Show Details > >> > >> On 04/02/2018 18:13, Steve Grubb wrote: > >> > >>> Hello, > > >>> + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 > >>> error: Bad exit status from /home/sgrubb/working/tmp/rpm-tmp.tz0qAN > > >> Full build log, please. > > > > It's too big for the mail list. I put it here: > > > > http://people.redhat.com/sgrubb/files/build.log > > Many questions here, and a large package. Still, searching the logs I > cannot see any python files - are there any such at all? None at all. Its all java, javascript, R, and ELF files. > If not, perhaps you could disable the byte compulation as described in > [1]? Bingo! That fixed the build...which leads to the question of why is that failing? > Another question: brp-python-bytecompile tries to use /usr/bin/python > which still is python2.7 (I think). So, have you a BR: python2-devel, or > is the python command just missing in the build environment? This is being built on my local system. Its has both available: # rpm -qa | grep python | grep devel python2-devel-2.7.14-7.fc27.x86_64 python3-devel-3.6.4-7.fc27.x86_64 But this package uses no python anywhere. So, its strange that the build is getting tripped up on python. Thanks for the help. This should let me release an Rstudio 1.1 srpm shortly. Thanks, -Steve _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
