Description of problem: I get the following errors on installation of kernel and kernel-devel 2.6.26- 136.f10 For kernel: /sbin/ldconfig: /lib/ld-linux.so.2 is not a symbolic link For kernel-devel: /var/tmp/rpm-tmp.92170: line 12: : command not found error: %post(kernel-devel-2.6.26-136.fc10.i686) scriptlet failed, exit status 127 Version-Release number of selected component (if applicable): kernel-2.6.26-136.fc10 How reproducible: Always Steps to Reproduce: 1.yum install kernel kernel-devel 2. 3. Actual results: Error messages given above Expected results: No error messages Additional info: Up to and including kernel-2.6.26-0.131.fc9.git9.fc10 I didn't get the error messages. BTW, should fedora_cvs_origin have been set to 760 for the 2.6.26 released kernel?
two separate bugs here. /sbin/ldconfig: /lib/ld-linux.so.2 is not a symbolic link is a mkinitrd bug. (reassigned). The other.. For kernel-devel: /var/tmp/rpm-tmp.92170: line 12: : command not found error: %post(kernel-devel-2.6.26-136.fc10.i686) scriptlet failed, exit status is a mystery. Can you cat /var/tmp/rpm-tmp.92170 and find out what command its barfing on?
Created attachment 311766 [details] /var/tmp/rpm-tmp.59649 file created by yum install kernel-devel
I attach a new /var/tmp/rpm-tmp.nnnnn from a re-install. It is not easy to catch since it only exists for a few milli-seconds. There appears to be a stray \x19 (^Y) character at end of the file (line 12)
That looks like an rpm bug. I recommend leaving this one for Peter to take care of mkinitrd, and file a seperate one for the rpm bug.
rpm bug filed as 455333
Just FYI, the junk at end of script was a bug in rpm macro argument handling (a build, not runtime issue) which should be fixed now in rpm-4.5.90-0.git8426.8 which just finished building. The kernel spec is pretty heavy on macros making it a likely candidate for catching regressions in that area...
Has this still been an issues Quentin or can we close this as fixed in rawhide?
Closing this as fixed, since I can no longer reproduce this. If it is not fixed in the Preview release, please reopen.