Rex Dieter wrote: > Rex Dieter wrote: > >> Stuart Jansen wrote: >> >>> I recently upgraded an internal build server from C5.2 to C5.3 and now >>> I'm experiencing problems initializing the mock buildroot. Specifically, >>> I'm getting the following error: >>> >>> ------ >>> /var/tmp/rpm-tmp.77062: line 6: cat: command not found >>> /var/tmp/rpm-tmp.77062: line 7: rm: command not found >>> /var/tmp/rpm-tmp.77062: line 22: install: command not found >>> /var/tmp/rpm-tmp.77062: line 25: install: command not found >>> error: %post(pam-0.99.6.2-4.el5.i386) scriptlet failed, exit status 127 >>> --- >> I saw this in my f10 buildroots hosted on centos 5.2. >> >> several bugs: >> 1. rpm/yum (on the buildhost) not respecting pam's >> Requires(post): coreutils >> 2. pam's scriptlets unsafe and not ending with ||: >> 3. rpm/yum (on the buildhost) exiting with error-code on a scriptlet >> failure (and mock aborting because of it). I'm fairly certain recent >> rpm/yum on fedora no longer suffers from this. >> >> I emailed pam's maintainers about item 2 ~6 months ago, but I don't see it >> implemented yet. I guess I never filed a bug, will do now. > > interestingly, I can no longer reproduce this failure myself on a recently > upgraded centos-5.3 box using mock-0.9.14 (from epel). i've got exactly the same thing and not able to solve it. some can tell me what was the solution for him? thanks in advance. -- Levente "Si vis pacem para bellum!"