Bug 201871 - error when doing yum upgrade "autofs conflicts with kernel < 2.6.17"
Summary: error when doing yum upgrade "autofs conflicts with kernel < 2.6.17"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: autofs
Version: 6
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Moyer
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-09 15:33 UTC by Steve Barnhart
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-08-09 17:52:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Steve Barnhart 2006-08-09 15:33:42 UTC
Description of problem:
Was doing yum upgrade from FC5 to FC6 test2 after installing new fedora-release
and fedora-release-notes packages. Went fine until got around to here...

 Package perl-IO-Zlib.noarch 0:1.04-4.2.1 set to be updated
---> Downloading header for perl-Net-SSLeay to pack into transaction set.
perl-Net-SSLeay-1.30-4.fc 100% |=========================|  16 kB    00:00
---> Package perl-Net-SSLeay.i386 0:1.30-4.fc6 set to be updated
--> Running transaction check
--> Processing Conflict: autofs conflicts kernel < 2.6.17
--> Finished Dependency Resolution
Error: autofs conflicts with kernel < 2.6.17


Version-Release number of selected component (if applicable):
autofs-4.1.4-29 installed atleast after this error and
 2.6.17-1.2157_FC5smp..which is weird cuz it is 2.6.17. This was after the
update though of course so two kernels are still in grub and everything (used to
have 2.6.15-1.2054_FC5smp).

How reproducible:
try a yum upgrade..maybe keep default fedora kernel around idk

Steps to Reproduce:
1.
2.
3.
  
Actual results:
ends with error reported above

Expected results:
to actually upgrade everything lol

Additional info:

Comment 1 Jeff Moyer 2006-08-09 17:52:19 UTC
Reboot, get rid of the older kernel, try your yum upgrade again.


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