On Sat, Jun 19, 2010 at 12:16 AM, Bruno Wolff III <bruno@xxxxxxxx> wrote:
What's this spec file? How do you use conflicts?
How do I make "if" less iffy?
You'll have to explain this whole process. I'd be very surprised if a repository not belonging to Red Hat/Fedora could prevent a kernel upgrade or any upgrade. This could eb dangerous.
If you remember the beginning of this discussion, we were talking about the problems the missing kmod could occcasion to <B>newbies</B>. I always check that the corresponding kmod is there and if I'd ever forget, it would be no problem reverting to the previous kernel. But a newbie might decide that "this thing doesn't work" and go back to Windows.
Your "solution" is not a solution for newbies.
Now, here's the upgrade suggestion I received today:
Package kernel.x86_64 0:2.6.32.14-127.fc12 set to be installed
---> Package kernel-firmware.noarch 0:2.6.32.14-127.fc12 set to be updated
---> Package kernel-headers.x86_64 0:2.6.32.14-127.fc12 set to be updated
---> Package kmod-nvidia.x86_64 1:195.36.24-1.fc12.3 set to be updated
--> Processing Dependency: kmod-nvidia-2.6.32.14-127.fc12.x86_64 >= 1:195.36.24-1.fc12.3 for package: 1:kmod-nvidia-195.36.24-1.fc12.3.x86_64
kernel x86_64 2.6.32.14-127.fc12 updates 21 M
kernel-firmware noarch 2.6.32.14-127.fc12 updates 973 k
kernel-headers x86_64 2.6.32.14-127.fc12 updates 754 k
kmod-nvidia x86_64 1:195.36.24-1.fc12.3 rpmfusion-nonfree-updates 31 k
It somehow doesn't seem to me like a standard upgrade...
On Fri, Jun 18, 2010 at 22:02:49 -0400,
> As I said, I don't believe rpmfusion, a repository not supported by RedThey can using 'conflicts' in the spec file.
> Hat/Fedora, could block a kernel update.
What's this spec file? How do you use conflicts?
If the kmod is installed first,
How do I make "if" less iffy?
You'll have to explain this whole process. I'd be very surprised if a repository not belonging to Red Hat/Fedora could prevent a kernel upgrade or any upgrade. This could eb dangerous.
You can also set your system so that the default boot kernel doesn't change
when there is a kernel update. This protects you from the kmod being released
late problem at the cost of having to manually switch boot kernels after
every kernel + kmod update.
If you remember the beginning of this discussion, we were talking about the problems the missing kmod could occcasion to <B>newbies</B>. I always check that the corresponding kmod is there and if I'd ever forget, it would be no problem reverting to the previous kernel. But a newbie might decide that "this thing doesn't work" and go back to Windows.
Your "solution" is not a solution for newbies.
Now, here's the upgrade suggestion I received today:
Package kernel.x86_64 0:2.6.32.14-127.fc12 set to be installed
---> Package kernel-firmware.noarch 0:2.6.32.14-127.fc12 set to be updated
---> Package kernel-headers.x86_64 0:2.6.32.14-127.fc12 set to be updated
---> Package kmod-nvidia.x86_64 1:195.36.24-1.fc12.3 set to be updated
--> Processing Dependency: kmod-nvidia-2.6.32.14-127.fc12.x86_64 >= 1:195.36.24-1.fc12.3 for package: 1:kmod-nvidia-195.36.24-1.fc12.3.x86_64
kernel x86_64 2.6.32.14-127.fc12 updates 21 M
kernel-firmware noarch 2.6.32.14-127.fc12 updates 973 k
kernel-headers x86_64 2.6.32.14-127.fc12 updates 754 k
kmod-nvidia x86_64 1:195.36.24-1.fc12.3 rpmfusion-nonfree-updates 31 k
It somehow doesn't seem to me like a standard upgrade...
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
