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 ------
Googling has revealed that Fedora had a similar problem about a year ago, but doesn't reveal what to do about it. Apparently there is a circular dependency between pam and coreutils. For some reason yum has recently decided to install pam before coreutils.
Has anyone else seen this? More importantly, does anyone have any tips how to resolve or work around the issue?
On Thu, Apr 09, 2009, 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
This looks like the PATH environment variable is not set properly in the RPM build script (or your /bin/ directory is missing which would cause severe heartburn :-).
Bill
On Thu, 2009-04-09 at 16:54 -0700, Bill Campbell wrote:
On Thu, Apr 09, 2009, 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
This looks like the PATH environment variable is not set properly in the RPM build script (or your /bin/ directory is missing which would cause severe heartburn :-).
Except that isn't _my_ RPM. I'm trying to build a python package. This is happening during the initial phase when mock creates a build chroot by yum installing required build RPMs.
Stuart Jansen wrote:
On Thu, 2009-04-09 at 16:54 -0700, Bill Campbell wrote:
On Thu, Apr 09, 2009, 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
This looks like the PATH environment variable is not set properly in the RPM build script (or your /bin/ directory is missing which would cause severe heartburn :-).
Except that isn't _my_ RPM. I'm trying to build a python package. This is happening during the initial phase when mock creates a build chroot by yum installing required build RPMs.
*ack*
Same thing here when trying to initialize the buildroot with `mock init -r centos-5-i386.cfg --debug`
/var/tmp/rpm-tmp.15029: line 6: cat: command not found /var/tmp/rpm-tmp.15029: line 7: rm: command not found /var/tmp/rpm-tmp.15029: line 22: install: command not found /var/tmp/rpm-tmp.15029: line 25: install: command not found error: %post(pam-0.99.6.2-4.el5.i386) scriptlet failed, exit status 127
But that doesn't happen with x86_64 though .. To be investigated
On 04/09/09 16:46, Stuart Jansen enlightened us:
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
Googling has revealed that Fedora had a similar problem about a year ago, but doesn't reveal what to do about it. Apparently there is a circular dependency between pam and coreutils. For some reason yum has recently decided to install pam before coreutils.
Has anyone else seen this? More importantly, does anyone have any tips how to resolve or work around the issue?
I just started seeing this in the last week as well. I hadn't had time to start digging into it, though.
Matt
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.
-- Rex
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:
- 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).
-- Rex
On Mon, Apr 13, 2009 at 7:18 AM, Rex Dieter rdieter@math.unl.edu wrote:
interestingly, I can no longer reproduce this failure myself on a recently upgraded centos-5.3 box using mock-0.9.14 (from epel).
So, we can use mock-0.9.14 from EPEL on CentOS 5.3 (with the current CentOS yum) without any issue?
Akemi
Akemi Yagi wrote:
On Mon, Apr 13, 2009 at 7:18 AM, Rex Dieter rdieter@math.unl.edu wrote:
interestingly, I can no longer reproduce this failure myself on a recently upgraded centos-5.3 box using mock-0.9.14 (from epel).
So, we can use mock-0.9.14 from EPEL on CentOS 5.3 (with the current CentOS yum) without any issue?
of course. (what would make you think otherwise?)
-- Rex
On Mon, Apr 13, 2009 at 7:47 AM, Rex Dieter rdieter@math.unl.edu wrote:
Akemi Yagi wrote:
So, we can use mock-0.9.14 from EPEL on CentOS 5.3 (with the current CentOS yum) without any issue?
of course. (what would make you think otherwise?)
Well, I heard from one of the CentOS devs that mock newer than 0.6 was broken. But this was a long time (> 1 year) ago. Moreover, yum 3.x used to have some issues. Because of these, I have been running mock on a CentOS-4 box and wondered if I could make a switch to CentOS-5.
Akemi
Akemi Yagi wrote:
On Mon, Apr 13, 2009 at 7:47 AM, Rex Dieter rdieter@math.unl.edu wrote:
Akemi Yagi wrote:
So, we can use mock-0.9.14 from EPEL on CentOS 5.3 (with the current CentOS yum) without any issue?
of course. (what would make you think otherwise?)
Well, I heard from one of the CentOS devs that mock newer than 0.6 was broken.
OK, fair 'nuf. Just seemed silly to me that you'd assume epel would release something that was broken.
-- Rex
On 04/13/2009 04:43 PM, Rex Dieter wrote:
Well, I heard from one of the CentOS devs that mock newer than 0.6 was broken.
OK, fair 'nuf. Just seemed silly to me that you'd assume epel would release something that was broken.
EPEL releases broken stuff all the time :)
Also mock > 0.6 doesnt work properly on c3/c4 - and mock 0.9.x is different enough to produce inconsistent builds with mock 0.6, which is why were sticking to mock 0.6 for the time being, within CentOS.
Karanbir Singh wrote:
On 04/13/2009 04:43 PM, Rex Dieter wrote:
Well, I heard from one of the CentOS devs that mock newer than 0.6 was broken.
OK, fair 'nuf. Just seemed silly to me that you'd assume epel would release something that was broken.
EPEL releases broken stuff all the time :)
Also mock > 0.6 doesnt work properly on c3/c4 - and mock 0.9.x is different enough to produce inconsistent builds with mock 0.6, which is why were sticking to mock 0.6 for the time being, within CentOS.
on centos-5.2 mock-0.9.x was working properly. now neither mock not even rpmbuild working for us (this second is another probably rpm bug which is just investigating). anyway you suggest to use mock 0.6 on 5.3? thanks.
Farkas Levente wrote:
Karanbir Singh wrote:
On 04/13/2009 04:43 PM, Rex Dieter wrote:
Well, I heard from one of the CentOS devs that mock newer than 0.6 was broken.
OK, fair 'nuf. Just seemed silly to me that you'd assume epel would release something that was broken.
EPEL releases broken stuff all the time :)
Also mock > 0.6 doesnt work properly on c3/c4 - and mock 0.9.x is different enough to produce inconsistent builds with mock 0.6, which is why were sticking to mock 0.6 for the time being, within CentOS.
on centos-5.2 mock-0.9.x was working properly. now neither mock not even rpmbuild working for us (this second is another probably rpm bug which is just investigating). anyway you suggest to use mock 0.6 on 5.3? thanks.
it turns out as we downgrade to 5.2's rpm*, popt packages both our rpmbuild problem and mock-0.9.x problems goes away. so it seems there is/are some kind of rpm bug in 5.3.
On Mon, Apr 13, 2009 at 8:47 AM, Rex Dieter rdieter@math.unl.edu wrote:
Akemi Yagi wrote:
On Mon, Apr 13, 2009 at 7:18 AM, Rex Dieter rdieter@math.unl.edu wrote:
interestingly, I can no longer reproduce this failure myself on a recently upgraded centos-5.3 box using mock-0.9.14 (from epel).
So, we can use mock-0.9.14 from EPEL on CentOS 5.3 (with the current CentOS yum) without any issue?
of course. (what would make you think otherwise?)
It supposedly has problems with EL-2/3/4 builds.
I am having this problem with EPEL mock-0.9.14 on i386.. so I am guessing there is some thing different between environments.
On Mon, 2009-04-13 at 07:26 -0700, Akemi Yagi wrote:
On Mon, Apr 13, 2009 at 7:18 AM, Rex Dieter rdieter@math.unl.edu wrote:
interestingly, I can no longer reproduce this failure myself on a recently upgraded centos-5.3 box using mock-0.9.14 (from epel).
So, we can use mock-0.9.14 from EPEL on CentOS 5.3 (with the current CentOS yum) without any issue?
I'm using mock-0.9.14 on a fully updated CentOS 5.3 and yum is still trying to install pam before coreutils.
Perhaps the problem is a configuration difference. For the most part, I'm using a standard mock configuration. I have, however, disabled all caching in site-defaults.cfg
Perhaps others aren't seeing this problem yet because they are using a cached buildroot, but will have a problem once the cache is cleared. I tried enabling caching, but it didn't make a difference.
For building, I use a copy of the CentOS core and update packages rsync'd from a local mirror.
rsync -qaHz --numeric-ids --fuzzy --delete-excluded
I'm also using the latest buildsys packages from Fedora downloaded by runnning:
wget -q -rc -nv -nH -np -R '*=D,*=A' \ http://buildsys.fedoraproject.org/buildgroups/rhel5/i386/
I have tried building with EPEL enabled and disabled. Neither helped.
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:
- 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.
Rex Dieter wrote:
Rex Dieter wrote
/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
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 take it back. mock -r epel-5-i386 fails, but a home-brewed but almost identical to that config doesn't, digging into the differences now.
-- Rex
Rex Dieter wrote:
Rex Dieter wrote:
Rex Dieter wrote
/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
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 take it back. mock -r epel-5-i386 fails, but a home-brewed but almost identical to that config doesn't, digging into the differences now.
imho _many_ people would like to know the solution...
Farkas Levente napsal(a):
imho _many_ people would like to know the solution...
Well, solution is easy. Make sure pam is installed before the coreutils. :o) Now seriously. 32bit and 64bit pam packages come from the very same source, so both have to be installed after coreutils and that it is not so is the other thing. It may be rpm or yum "bug". The workaround for the time being is to use patched pam package. The patch is: Requires(post): coreutils, /sbin/ldconfig
There's package available within one of my testing repos. http://fs12.vsb.cz/hrb33/el5/hrb/testing/i386/
Regards, David Hrbáč
-
Akemi Yagi -
Bill Campbell -
David Hrbáč -
Fabian Arrotin -
Farkas Levente -
Karanbir Singh -
Matthew Hyclak -
Rex Dieter -
Stephen John Smoogen -
Stuart Jansen