Bug 834738 - apper and yum will not update to new KERNEL
Summary: apper and yum will not update to new KERNEL
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Fedora Packaging Toolset Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-23 03:36 UTC by david
Modified: 2014-01-21 23:22 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-23 09:25:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description david 2012-06-23 03:36:02 UTC
Description of problem:


Version-Release number of selected component (if applicable):Fedora 17


How reproducible:every time you try to update


Steps to Reproduce:
1.utilising either yum or apper gives the same errorsERROR with transaction check vs depsolve:
kernel-uname-r = 2.6.42.12-1.fc15.x86_64 is needed by kmod-nvidia-2.6.42.12-1.fc15.x86_64-1:280.13-2.fc15.26.x86_64
kernel-uname-r = 2.6.43.2-6.fc15.x86_64 is needed by kmod-nvidia-2.6.43.2-6.fc15.x86_64-1:280.13-4.fc15.3.x86_64
kernel-uname-r = 2.6.43.5-2.fc15.x86_64 is needed by kmod-nvidia-2.6.43.5-2.fc15.x86_64-1:280.13-4.fc15.5.x86_64
Please report this error at
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Kevin Kofler 2012-06-23 09:25:35 UTC
If anything, this is a yum bug, but I think the problem will simply go away when kmod-nvidia gets updated in RPM Fusion to match the new kernel. It's normal that third-party kernel module updates are pushed only approximately at the same time as the kernel update they match, not exactly at the same time.


Note You need to log in before you can comment on or make changes to this bug.