On 03/10/2014 02:22 PM, Matthew Miller wrote: > When Fedora is in a container (a la Docker), the kernel comes > from the host, not the installed package set. I noticed a number of packages > which actually have a requirement on the kernel package. This isn't very > helpful, since the installed package says nothing about the running one, and > forcing the package doesn't help. > > For many of these, the requirement is actually that the running kernel have > a certain feature, and the hope is that the package version check will do > it. For others, like ipset, I'm not quite sure -- there's a spec file > comment that says "This is developed hand in hand with a kernel module", but > it then just says "Requires: kernel". > > I think quemu-sanity-check may be the only one that actually really wants a > kernel. Possibly libguestfs too -- I didn't dig too deepy. > > There aren't actually a lot: ... > systemtap-devel / systemtap-runtime (from systemtap) I've checked in a change to systemtap's upstream spec file that should fix this. It should be present for the next rawhide build on Monday. <https://www.sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commitdiff;h=92319a32b14defa5c6344314d3a88a1cf2baff71> -- David Smith dsmith@xxxxxxxxxx Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax) -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
