Re: mock rpmdb version issue with epel-5-i386 target

2009-09-16 Thread Panu Matilainen
On Mon, 14 Sep 2009, Mike McLean wrote: On 09/14/2009 11:50 AM, Alan Franzoni (mailing) wrote: It seems the rpmdb of the chroot has been created with an rpm employing a different format ( I can assume it's the 'host' system rpm ), hence leading to a format mismatch which prevents from using

Re: mock rpmdb version issue with epel-5-i386 target

2009-09-15 Thread Mike McLean
On 09/14/2009 05:13 PM, Jason L Tibbitts III wrote: MM I suppose we should add a way to access the yum localinstall MM functionality through mock. I have done this for years: echo Installing built packages: runmock -v --install $MOCKDIR/result/*{i386,x86_64,noarch}.rpm 21 (dependent on the

Re: mock rpmdb version issue with epel-5-i386 target

2009-09-15 Thread Seth Vidal
On Tue, 15 Sep 2009, Mike McLean wrote: On 09/14/2009 05:13 PM, Jason L Tibbitts III wrote: MM I suppose we should add a way to access the yum localinstall MM functionality through mock. I have done this for years: echo Installing built packages: runmock -v --install

Re: mock rpmdb version issue with epel-5-i386 target

2009-09-15 Thread Alan Franzoni
2009/9/15 Mike McLean mi...@redhat.com: [cut] I think I got all the info I need, and I wish to thank you all for your excellent and prompt support! -- Alan Franzoni -- contact me at pub...@[mysurname].eu -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com

Re: mock rpmdb version issue with epel-5-i386 target

2009-09-14 Thread Mike McLean
On 09/14/2009 01:13 PM, Jesse Keating wrote: Note that you'll have rpmdb mismatches even when creating an EL5 chroot on EL5, if you create an i386 chroot on an x86_64 host. Just that difference is enough to cause rpmdb mismatches. A work around if you must work within the chroot is to remove