I spotted a couple of points where I think the Koji documentation could be
improved:
In Koji/ServerHowTo#Koji_filesystem_skeleton you give an example
kojiadmin@localhost$ koji add-host kojibuilder1 x86_64 i386
which looks as if a simple user name style is sufficient. Near the end of
the same document, in
Koji/ServerHowTo#Add_the_host_entry_for_the_koji_builder_to_the_database,
you say it like this:
kojiadmin@localhost$ koji add-host
kojibuilder1.example.com i386 x86_64
Now it looks as if you're supposed to use the full host name, not a user
name. It would be good to make those entries consistent and, if you do need
the FQDN, to explain why.
In
Koji/ExternalRepoServerBootstrap#Bootstrapping_a_new_External_Repo_Koji_buil
d_environment you have a note
* NOTE: 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 -p flag to set specific repo priorities.
That suggests that repos with newer packages should be added first:
testing/\$arch
updates/\$arch
os/\$arch
However in
Koji/ExternalRepoServerBootstrap#Examples_of_urls_to_use_for_external_Reposi
tories your examples list the os release repo before the updates repo,
which would give the repo with the older packages the lower numeric value
and therefore the higher priority.
Moray.
"To err is human; to purr, feline."
OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3 0JG - United
Kingdom
Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)