caching packages on koji builder
Dan Horák
dan at danny.cz
Thu Nov 6 10:55:22 UTC 2008
Mike McLean píše v St 05. 11. 2008 v 15:14 -0500:
> Mike McLean wrote:
> > This behavior is controlled by kojid options. If you specify the
> > 'topurl' option for kojid, then the mock configs it generates will use
> > an http:// url to point to the repo. Otherwise it will use a file:// url
> > (using the value of the 'topdir' option, which defaults to /mnt/koji).
> >
> > Also, the use of a file:// url doesn't have to mean nfs. You could
> > theoretically use another shared file system.
>
> So this is true, but misleading. The interaction of the topurl and
> pkgurl options in kojid is complicated.
>
> The topurl/topdir options determine how kojid will locate the repo.
> However, with the current code, the repodata will contain url references
> for the component rpms. That url is determined when the repo is
> generated. This happens during a createrepo task on a builder, and the
> pkgurl (not topurl) option is used.
>
> So..
> - repodata location determined by topurl/topdir options
> - rpm location determined by pkgurl option on the builder that created
> the repo.
>
> I admit, this is a bit of a mess.
And I am lost there :-)
Squid runs, url_rewriter works and I am still unable to cache the
packages. What value is placed into the mock generated yum config?
Dan
More information about the buildsys
mailing list