On Mon, 24 Mar 2008 10:20:26 -0400, Thomas J. Baker wrote:
On Mon, 2008-03-24 at 12:22 +0000, Richard W.M. Jones wrote:
> On Mon, Mar 24, 2008 at 11:53:33AM +0100, Michael Schwendt wrote:
> > AFAIK, the packages must be listed in the repodata for the resolve step to
> > be successful. Installing directly into the guest rpm db is not enough.
> > And when updating the repodata to be used by mock+yum, be sure to disable
> > the metadata_expire value, so updated repos are recognised always.
>
> Any hint about how I do this?
You need to modify your /etc/mock/whatever-you-use.cfg file to point
to
a local repository. I've got one like this:
[mock-updates]
name=mock-updates
baseurl=file:///net/home/rcc/tjb/mock-updates/8/x86_64/
I have a simple script (attached) that moves the results of one build
into my local mock-updates repo and runs createrepo to make it a valid
repository. So build A, run script, build B which needs A, and it should
work.
Plus you can edit the mock build target cfg file to add metadata_expire=0
in the config_opts['yum.conf'] section.