On Tue, 2013-06-04 at 11:05 -0400, seth vidal wrote: > On Tue, 4 Jun 2013 16:52:14 +0200 > Simone Caronni <negativo17@xxxxxxxxx> wrote: > > > Hello, > > > > I have a package that builds fine in a fresh rawhide mock chroot and > > not in a koji build. Is there any difference between the two? > > > > Here is the error in Koji: > > > > + make -j5 LIBPATH=/usr/lib64 -f makefile docs > > rm -f doc/crypt.pdf *.dvi *.log *.aux *.toc *.idx *.ilg *.ind *.out > > echo "hello" > crypt.ind > > latex crypt > /dev/null > > kpathsea: Running mktexfmt latex.fmt > > make: *** [docs] Error 1 > > RPM build errors: > > error: Bad exit status from /var/tmp/rpm-tmp.5TWg4P (%build) > > Bad exit status from /var/tmp/rpm-tmp.5TWg4P (%build) > > > > And here is the same step in mock: > > > > DEBUG: + make -j4 LIBPATH=/usr/lib64 -f makefile docs > > DEBUG: rm -f doc/crypt.pdf *.dvi *.log *.aux *.toc *.idx *.ilg *.ind > > *.out DEBUG: echo "hello" > crypt.ind > > DEBUG: latex crypt > /dev/null > > DEBUG: latex crypt > /dev/null > > DEBUG: makeindex crypt.idx > /dev/null > > DEBUG: This is makeindex, version 2.15 [TeX Live 2013] (kpathsea + > > Thai support). > > DEBUG: Scanning input file crypt.idx....done (345 entries accepted, 0 > > rejected). > > DEBUG: Sorting entries......done (3023 comparisons). > > DEBUG: Generating output file crypt.ind....done (396 lines written, 0 > > warnings). > > DEBUG: Output written in crypt.ind. > > [...] > > > > Log of the failed koji build: > > > > http://kojipkgs.fedoraproject.org//work/tasks/4779/5464779/build.log > > > > Command used for mock: > > > > mock -v --rebuild -r fedora-rawhide-x86_64 > > libtomcrypt-1.17-16.fc19.src.rpm > > > > Koji uses mock to build pkgs. > > Mock in Koji is run on systems which are isolated from the network. > > If there is no network connection then there shouldn't be any difference I note 'make -j5' vs 'make -j4': Simone has more parallelization capability than mock, it seems. Simone, you could fiddle with your spec file so it doesn't do a parallel build at all, and see if the build starts working then. If so, report to upstream that their build process is not entirely safe for parallelization. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
