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? > > Rich. > > -- > Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones > virt-top is 'top' for virtual machines. Tiny program with many > powerful monitoring features, net stats, disk stats, logging, etc. > http://et.redhat.com/~rjones/virt-top > 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. Thanks, tjb -- ======================================================================= | Thomas Baker email: tjb@xxxxxxx | | Systems Programmer | | Research Computing Center voice: (603) 862-4490 | | University of New Hampshire fax: (603) 862-1761 | | 332 Morse Hall | | Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb | =======================================================================
Attachment:
moveMock
Description: C-Shell script
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
