| Summary: | em8300-kmod-common (required by kmod-em8300-nnn) not provided | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | jon.fairbairn |
| Component: | em8300-kmod | Assignee: | Felix Kaechele <felix> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | fedora, kwizart, walrus |
| Priority: | P5 | ||
| Version: | 11 | ||
| Hardware: | All | ||
| OS: | GNU/Linux | ||
| namespace: | |||
|
Description
jon.fairbairn
2009-07-26 16:35:39 CEST
em8300 0.17.3 is currently sitting in updates-testing for 9 days already. So I think we have to wait until it is moved into stable. The update should work then. Also see: https://admin.fedoraproject.org/updates/F10/FEDORA-2009-7881 https://admin.fedoraproject.org/updates/F11/FEDORA-2009-7838 It seems to me that when fedora releases a new kernel, kmod-em8300 should be rebuilt for that kernel against the version of em8300 (-common) that exists in the fedora repo. So rebuilding of kmod-em8300 would be triggered by two different events: new kernel, and new em8300. I'm having a very similar problem with Fedora *12* five months later using akmod-em8300 instead. Is this really fixed? em8300-kmod-common >= 0.17.4 is needed by package akmod-em8300-0.17.4-1.fc12.1.i686 (rpmfusion-free-updates) I DON'T see an updates testing package at all to satisfy this, nor is there anything in development that is different from what is available through yum normally. The devel and utils pacakges are out of date, too (as in, not the same version of the other em8300 packages). I'm reopening this bug. However, perhaps this should be published on the Red Hat Bugzilla? The packages in question are on the Fedora repositories (or, at least from what I understand, they should be). Someone please let me know. |