Description of problem: I tried the "new pkg format" by downloading from koji the PAE packages and installing via "rpm -ivh .....". The install failed: [root@localhost Downloads]# rpm -ivh *PAE* Preparing... ########################################### [100%] 1:kernel-PAE ########################################### [ 50%] 2:kernel-PAE-devel ########################################### [100%] Usage: new-kernel-pkg [-v] [--mkinitrd] [--rminitrd] [--initrdfile=<initrd-image>] [--depmod] [--rmmoddep] [--kernel-args=<args>] [--remove-args=<args>] [--banner=<banner>] [--multiboot=multiboot] [--mbargs=mbargs] [--make-default] <--install | --remove | --update | --rpmposttrans> <kernel-version> (ex: new-kernel-pkg --mkinitrd --depmod --install 2.4.7-2) error: %posttrans(kernel-PAE-2.6.25-0.155.rc6.git8.fc9.i686) scriptlet failed, exit status 1 [root@localhost Downloads]# Did not get this message installing the non-PAE package via yum. Version-Release number of selected component (if applicable): kernel-PAE-2.6.25-0.155.rc6.git8.fc9.i686.rpm How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Gah. Digging into it now...
This is actually a tiny buglet in the posttrans hook, not something directly related to changing uname -r around, but I'm not sure why it wasn't triggering before now (or if it just went unnoticed)... In any case, fix committed to kernel-2.6.25-0.160.rc7.fc9, so anything that build or later should be good to go now.