Open main menu

CDOT Wiki β

Changes

Fall 2010 SBR600 Weekly Schedule

46 bytes added, 21:56, 16 September 2010
mock: Testing BuildRequires
It's often difficult to get the BuildRequires in a spec file exactly right, because it's easy to overlook packages that are coincidentally installed on the machine. <code>mock</code> is a tool that uses the chroot system call to create a "cleanroom" environment for the build, so that any missing BuildRequires cause the build to fail.
{{Admon/note|The '''mock''' Group|To use mock, you will need to add yourself to the '''mock''' group.: <code>usermod -G mock ''yourUserName''</code>}}
To build with mock:
mock -r ''fedora-1213-x86_64'' --rebuild ''foo*.src.rpm''
The value ''fedora-1213-x86_64'' may be changed to any of the config files found in <code>/etc/mock</code> in order to test building based on the libraries and available packages for a specific architecture and Fedora release. If errors are reported, review the log files (see the mock output to determine the directory containing the log files).
== koji: Testing multiple architectures ==