On Fri, Apr 6, 2012 at 2:00 PM, Simon Wilkinson <simonxwilkin...@gmail.com> wrote: > This looks like mock is evaluating the srpm outside of the chroot. Given that > we know that this works with the mock from EPEL (1.1.22) could you try > running your test with that version?
I've been testing trying to build 1.6.1 (and just tried with 1.6.0 too) with mock on RHEL6, using the mock package from there (mock-1.1.21-1.el6). For both the SRPM, I get this: ERROR: Command failed: # ['/usr/bin/yum-builddep', '--installroot', '/var/lib/mock/epel-5-x86_64/root/', '/var/lib/mock/epel-5-x86_64/root///builddir/build/SRPMS/openafs-1.6.1-1.el5.centos.src.rpm'] Getting requirements for openafs-1.6.1-1.el5.centos.src --> pam-devel-0.99.6.2-6.el5_5.2.x86_64 --> ncurses-devel-5.5-24.20060715.x86_64 --> flex-2.5.4a-41.fc6.x86_64 --> bison-2.3-2.1.x86_64 --> Already installed : 4:perl-5.8.8-38.el5.x86_64 --> krb5-devel-1.6.1-70.el5.x86_64 --> kernel-devel-2.6.18-308.1.1.el5.x86_64 Error: No Package found for kernel-devel-x86_64 = 2.6.18-308.1.1.el5-x86_64 I'm running this as my mock command: mock -v --define 'kernvers 2.6.18-308.1.1.el5-x86_64' -r epel-5-x86_64 openafs-1.6.1-1.src.rpm I think the define is required because otherwise it uses the output of `uname -r` to determine what kernel release to use. This normally works, which is why I'm confused. I know I built the 1.6.0 RPMs in mock when it came out, so something has changed in my environment. I'm not certain, but I think there might be a problem with the version of mock or yum in RHEL6 which is causing these problems for epel-5 systems. I'm trying to build from a SRPM built from git and I'm getting even stranger problems where it isn't even finding perl-devel (!). -- Jonathan Billings <jsbil...@umich.edu> College of Engineering - CAEN - Unix and Linux Support _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
