1,885
edits
Changes
→Queueing the Build Request
# You can either follow the progress of the build by leaving the command running, or you may interrupt the <code>koji</code> command by pressing Ctrl-C once the message "this may be safely interrupted" is printed. Record the ''taskID'' printed for future reference.
To queue the build request on the koji server for another architecture, substitute <code>''arch''-koji</code> for the <code>koji</code> command. For example: <code>s390-koji build ''f18'' --scratch ''foo*.src.rpm''</code>-- note that many of the koji servers handle multiple architectures -- e.g., the s390 server handles two architectures (s390 and s390x).
'''Use Koji to build a scratch package for each of the following architectures:'''
** x86_64 (64-bit AMD/Intel)
** armv7hl (32-bit ARM with FPU)
* s390 mainframe architectures(use the S390 koji server):
** s390
** s390x
* PowerPC architectures(use the PPC koji server):
** ppc (32-bit)
** ppc64 (64-bit)
* additional ARM architecture(use the armv6 koji server):
** armv6hl / Pidora (ARM architecture optimized for armv6 (Raspberry Pi))
*** '''Note:''' See [http://blog.chris.tylers.info/index.php?/archives/272-Acessing-the-armv6hl-Koji-Buildsystem.html this blog post] for details on accessing the Pidora koji system.
