Bug 507014 - yum.conf default handling of installonlypkgs doesn't match kernel-PAE
yum.conf default handling of installonlypkgs doesn't match kernel-PAE
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-19 16:22 EDT by Jason Roysdon
Modified: 2014-01-21 18:10 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-06-19 16:25:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jason Roysdon 2009-06-19 16:22:48 EDT
Description of problem:
"yum update" with F11 appears to try to preserve the "installonlypkgs" using the "installonly_limit=3" option.  Looking at man yum.conf lists the default "installonlypkgs" as "kernel, kernel-smp, kernel-bigmem, kernel-enterprise, kernel-debug, kernel-unsupported".

However, kernel-PAE is now installed by default on some systems.  As kernel-PAE isn't in this default "isntallonlypkgs" list, new versions are updated instead of installed.

I believe the fix would be to add this line to yum.conf:
installonlypkgs=kernel, kernel-smp, kernel-bigmem, kernel-enterprise, kernel-debug, kernel-unsupported, kernel-PAE

This will preserve the default yum.conf behavior, plus add kernel-PAE.

How reproducible:
Install F11 on system that has kernel-PAE by deault, or install kernel-PAE from CD/DVD after install.  Use yum update kernel*.

Steps to Reproduce:
1. rpm -i /path/to/F11-media/kernel-PAE*.rpm
2. yum update
3. rpm -q kernel-PAE
Actual results:
Only the newest kernel-PAE remains as it is updated, not installed.

Expected results:
Up to the 3 latest kernel-PAEs should be installed.
Comment 1 Jason Roysdon 2009-06-19 16:25:06 EDT
Ack, my apologies, as there has not been an F11 kernel update, and I misread my yum.log file thinking there should have been.  I don't yet know if this will be a bug or not.

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