On Thu, Jan 5, 2012 at 10:49 AM, John W. Linville <linville@xxxxxxxxxx> wrote: > On Thu, Jan 05, 2012 at 10:28:53AM -0500, Josh Boyer wrote: > >> > John, any thoughts if that might be the case? >> >> Answering my own question, it seems that is the case. This is at the >> end of the compat-wireless build: >> >> >> INSTALL /builddir/build/BUILD/kernel-3.1.fc16/compat-wireless-3.2-rc6-3/net/wireless/lib80211_crypt_wep.ko >> DEPMOD 3.1.7-1.fc16.x86_64 >> >> so depmod is getting called as a result of that. I'll look at fixing >> it up, one way or another. > > The compat-wireless Makefile rule in question does this: > > install-modules: modules > $(MAKE) -C $(KLIB_BUILD) M=$(PWD) $(KMODDIR_ARG) $(KMODPATH_ARG) \ > modules_install > > So that DEPMOD would seem to come from the kernel's modules_install rules. > > Why would the kernel spec file be picking-up those modules.* files anyway? We package them because they are created at install time. Makes for nicer upgrades and such so they get removed. During the build we delete them manually and rely on the %posttrans script to recreate them. What happened when compat-wireless was introduced is that we did the removal of the build generated ones before the compat-wireless stuff was built. So compat-wireless would build and then we'd be left with the files there we just deleted. I did a scratch build with that fixed and the rpm -V output is back to what it was with the 3.1.5 kernel: [jwboyer@zod linux-2.6]$ rpm -V kernel-3.1.7-3.fc16.x86_64 ?........ /boot/System.map-3.1.7-3.fc16.x86_64 ...T..... /lib/modules/3.1.7-3.fc16.x86_64/modules.devname ...T..... /lib/modules/3.1.7-3.fc16.x86_64/modules.softdep [jwboyer@zod linux-2.6]$ Should be fixed in the next f16 and rawhide builds that get done. josh -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
