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,
> > 
> > I am building a package locally and run across a failure that seems to be
> > unexplained. It gets to the install phase and then abruptly fails with
> > the
> > following build log:
> > 
> > -- Installing: /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/rpostback
> > -- Installing: /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/postback/rpostbac
> > k- askpass
> > -- Installing: /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/postback/rpostbac
> > k- editfile
> > -- Installing: /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/postback/rpostbac
> > k- gitssh
> > -- Installing: /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/postback/rpostbac
> > k- pdfviewer
> > -- Installing: /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/postback/askpass-
> > passthrough
> > + rm -rf /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64//usr/lib64
> > + /usr/lib/rpm/find-debuginfo.sh -j8 --strict-build-id -m -i
> > --build-id-seed 1.1.422-1.fc27 --unique-debug-suffix
> > -1.1.422-1.fc27.x86_64 --unique-debug- src-base
> > R-studio-desktop-1.1.422-1.fc27.x86_64 --run-dwz --dwz-low-mem-die-
> > limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list
> > /home/ sgrubb/working/BUILD/rstudio-1.1.422
> > extracting debug info from /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/rstudio
> > extracting debug info from /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/rsession
> > extracting debug info from /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/diagnostics
> > extracting debug info from /home/sgrubb/working/BUILDROOT/R-studio-
> > desktop-1.1.422-1.fc27.x86_64/usr/local/lib/rstudio/bin/rpostback
> > /usr/lib/rpm/sepdebugcrcfix: Updated 4 CRC32s, 0 CRC32s did match.
> > 15342 blocks
> > + /usr/lib/rpm/check-buildroot
> > + /usr/lib/rpm/brp-compress
> > + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
> > + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
> > error: Bad exit status from /home/sgrubb/working/tmp/rpm-tmp.tz0qAN
> > (%install)
> > 
> > RPM build errors:
> > Bad exit status from /home/sgrubb/working/tmp/rpm-tmp.tz0qAN (%install)
> > 
> > 
> > Is the output from sepdebugcrcfix indicating a failure? If so, how do you
> > fix this? If its not this, its really weird because there is plenty of
> > disk space and no other indication that something is wrong.
> > 
> > Thanks,
> > -Steve
> 
> Full build log, please.

It's too big for the mail list. I put it here:

http://people.redhat.com/sgrubb/files/build.log

-Steve


_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Reply via email to