External Repository Server Bootstrap¶
Bootstrapping a new External Repo Koji build environment¶
These are the steps involved in pointing a new Koji server at external
repositories so that it can be used for building. This assumes that the Koji
hub is up, appropriate authentication methods have been configured, the Koji
repo administration daemon (
kojira) is properly configured and running,
and at least one Koji builder (
kojid) is properly configured and running.
All koji cli commands assume that the user is a Koji
admin. If you need
help with these tasks, see the Server How To.
Create a new tag.
$ koji add-tag dist-foo
Create a build tag with the desired arches, and the previously created tag as a parent.
$ koji add-tag --parent dist-foo --arches "i386 x86_64 ppc ppc64" dist-foo-build
Add an external repository to your build tag. Koji substitutes $arch for the arches in your build tag. The
$needs to be escaped for the shell to send it though without interpreting it. See below for some additional examples of external repo URLs.
$ koji add-external-repo -t dist-foo-build dist-foo-external-repo http://repo-server.example.com/path/to/repo/for/foo/\$arch/
If you are adding multiple external repos, koji assigns a priority to each repo in FIFO order. This may cause updated packages to not be visible if a repo with older packages is ranked at a higher priority (lower numeric value). Use the
-pflag to set specific repo priorities.
This uses $arch NOT $basearch
Koji behaves differently to the external repository based on which
mergemode is set for that. Merge modes can be set via
-moption and are as follows:
Basic mode - koji expects, that that repo is complete and doesn’t contain mixed content. It means that only rpms from one SRPM can be present in repo for given package.
mergerepos_c --kojiRepositories generated via
dist-repocommand (and all other repositories coming from koji` has these properties.
mergerepos_c --pkgorigins --all. It includes all rpms with same package name and architecture even if version or release is different. This one is needed for modular repos.
createrepo_c0.14+ compiled with
libmodulesupport needs to be installed on the builder. Nevertheless, only the first rpm with identical NEVRA is accepted.
mergerepos_c --mode simple- we’re least restrivtive with this type of repo. Even packages with identical NEVRA are accepted in such case. Simple mode is in
createrepo_csuite from version 0.13. Reasons to use this compared to
baremode is a) you have older
createrepo_c, b) you really want to have all this identical NEVRAs in the repo.
Create a build target that includes the tags you’ve already created.
$ koji add-target dist-foo dist-foo-build
At this point you can verify that your external repository is set with the “taginfo” command. You should see it listed under “External repos”. Here is an example with several CentOS external repos:
$ koji taginfo dist-foo-build Tag: dist-foo-build  Arches: x86_64 Groups: build, srpm-build Tag options: This tag is a buildroot for one or more targets Current repo: repo#55077: 2017-11-29 03:34:18.847127 Targets that build from this tag: dist-foo External repos: 2 centos7-cr (http://mirror.centos.org/centos/7/cr/$arch/) 3 centos7-extras (http://mirror.centos.org/centos/7/extras/$arch/) 5 centos7-updates (http://mirror.centos.org/centos/7/updates/$arch/) 10 centos7-os (http://mirror.centos.org/centos/7/os/$arch/)
Create a ‘’build’’ and ‘’srpm-build’’ group associated with your build tag.
$ koji add-group dist-foo-build build $ koji add-group dist-foo-build srpm-build
srpm-buildgroup with packages that will be installed into the minimal buildroot. You can find out what the is in the current groups for Fedora by running
koji list-groups dist-f9-buildagainst the Fedora Koji instance. This is probably a good starting point for your minimal buildroot and srpm creation buildroot. If you are rebuilding Fedora packages, it is recommended that you add all packages listed in the Fedora Koji instance.
$ koji add-group-pkg dist-foo-build build <pkg1> <pkg2> .....
Add packages that you intend to build to your tag.
$ koji add-pkg --owner <kojiuser> dist-foo <pkg1> <pkg2> .....
Wait for the repo to regenerate, and you should now be able to run a build successfully.
Regenerating your repo¶
koji doesn’t monitor external repositories for changes by default.
Administrators can enable such bejaviour with setting
kojira.conf (for details see Koji Utilities). If it is not
enabled new repositories will be generated when packages you build land in a tag
that populates the buildroot or you manually regenerate the repository. you
should be sure to regularly regenerate the repositories manually to pick up
$ koji regen-repo dist-foo-build
Examples of urls to use for external Repositories¶
all these examples use mirrors.kernel.org please find the closest mirror to yourself. Note that the Fedora minimal buildroots download ~100Mb then build dependencies on top. these are downloaded each build you can save a lot of network bandwidth by using a local mirror or running through a caching proxy.
NOTE: this uses $arch NOT $basearch
CentOS 5 and EPEL¶
https://mirrors.kernel.org/centos/5/os/\$arch/ https://mirrors.kernel.org/centos/5/updates/\$arch/ https://mirrors.kernel.org/fedora-epel/5/\$arch/