Description of problem: I have a dxr3 card and when I installed Fedora 11 it installed em8300, apparently from the fedora repository, yum list em8300 Loaded plugins: refresh-packagekit Installed Packages em8300.x86_64 0.17.2-3.fc11 @fedora and I installed kmod-em8300 from rpmfusion. Now there's no em8300 available: yum list available em8300 Loaded plugins: refresh-packagekit Error: No matching Packages to list (that's fedora, fedora updates, rpmfusion, rpmfusion updates) Consequently yum won't update to the latest kmod-em8300 from rpmfusion Version-Release number of selected component (if applicable): em8300-kmod-common >= 0.17.3 see https://bugzilla.rpmfusion.org/show_bug.cgi?id=736 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Surely packages shouldn't just disappear?
Thank you for reporting the bug. As already stated in the RPMFusion Bugzilla the update for em8300 is in updates-testing. On my machines yum list available em8300 shows me that version 0.17.2-3.fc11 is available. However your kernel module is version 0.17.3-1.fc11.1 so it needs at least version 0.17.3 of the em8300 package. Packages in Fedora have a much longer time of staying in the testing repos than packages which are in RPMFusion. The new version of em8300, which is needed to install the new kmod will remain in testing for approximately 10 days (calculated from the average time my packages stayed in testing). Of course it is not good if a lag between Fedora and RPMFusion causes dependency breakage. But at this very moment there is not much I can do. I could always push em8300 updates to stable immediately (which would probably make some people frown) or issue em8300 updates 14 days before updating the kmod. Or I could think of moving em8300 into RPMFusion. I'll think about it and then report back with my choice. But for now the only think I could ask you for is your patience. You can still use yum update by using it with the --skip-broken parameter.
Ah, yes, sorry. I misunderstood the semantics of yum list available -- the output makes no distinction between "installed and available" and "installed". As to the main problem, is em8300 any use without kmod-em8300? If not, sending it to rpmfusion would seem the right thing to do. Looking at rpm -ql em8300, we see that there's some docs, /usr/bin/em8300setup for loading microcode, rules for udev -- which won't be triggered unless there's a kernel module available, console perms rules (ditto; there won't be device nodes to have permissions) and an alsa configuration file, again for a device that needs the kernel module. So I'd describe it as tightly bound to kmod-em8300. As to yum update, yes, that's what I've been doing (but it means I have to be careful not to boot with the latest kernel until there's a kmod for it)
The reason why em8300 is in Fedora is two-fold: 1) if em8300-devel was not available, other apps that need the header for building em8300 support would not be able to compile em8300 support in, and 2) at the time kmods were banished from Fedora, I thought it wouldn't take too long until em8300 modules would be included in mainline kernel (unfortunately it seems I was wrong about this).
OK, that's all sensible (except em8300 not being in the mainline kernel). So what caused my problem was that rpmfusion built kmod-em8300 for kernel-2.6.29.6-213 depending on a newer version of em8300-common than was available. If it was possible to build it against em8300-0.17.2-3.fc11.x86_64, they should surely have done that. I'll ask on my rpmfusion bug.
em8300 should be in sync now.