On Sun, 29 May 2011 22:59:41 +0800
Ed Greshko <Ed.Greshko(a)greshko.com> wrote:
On 05/29/2011 10:52 PM, Kevin Fenzi wrote:
> Then thats why. rpmfusion doesn't have one for your current kernel,
> but it does for the release kernel. Since that kernel is installed
> (even though it's not booted), it will meet the dep.
Seriously? It looks at what you've got installed, and not what is
currently running?
Yes. It looks at the rpm database to see whats installed.
How would looking at whats running work?
You would never get updates for programs you didn't happen to be
running when running the update command?
egreshko@meimei rpmfusion]$ rpm -q -R -p
kmod-nvidia-2.6.38.6-26.rc1.fc15.x86_64-270.41.06-1.fc15.x86_64.rpm
/bin/sh
/bin/sh
/sbin/depmod
/sbin/depmod
kernel-uname-r = 2.6.38.6-26.rc1.fc15.x86_64
^ equal, doesn't mean what is currently
running....but matches any installed kernel?
It matches any installed thing that provides that.
nvidia-kmod-common >= 1:270.41.06
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
That just seems like a disaster waiting to happen....
In what way?
You could install now and reboot in the old kernel and use it. ;)
kevin