Bug 1120806 - kernel-PAE.i686 doesn't have drpm
Summary: kernel-PAE.i686 doesn't have drpm
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-17 18:19 UTC by Naresh Sukhija
Modified: 2014-07-19 19:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-17 19:16:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Naresh Sukhija 2014-07-17 18:19:30 UTC
Description of problem:
There is no more drpm maintained for kernel-PAE.i686

Version-Release number of selected component (if applicable):
Fedora 20 kernel-PAE-3.15.5

How reproducible:


Steps to Reproduce:
1. Install kernel-PAE-3.15.4
2. Do yum update with deltarpm feature enabled
3. The next version of package Example kernel-PAE-3.15.5 will be downloaded fully instead of downloading the drpm

Actual results:
The next version of package Example kernel-PAE-3.15.5 will be downloaded fully instead of downloading the drpm

Expected results:
There needs to be drpm maintained for update from kernel-PAE-3.15.4 to kernel-PAE-3.15.5

Additional info:
The versions are just latest examples, I am observing this issue for few days/weeks now

Comment 1 Josh Boyer 2014-07-17 19:16:42 UTC
You need to file a ticket with the Fedora rel-eng trac instance.  They create the drpms.  The bugzilla component is for problems with the kernel itself.

Comment 2 Naresh Sukhija 2014-07-19 19:01:43 UTC
(In reply to Josh Boyer from comment #1)
> You need to file a ticket with the Fedora rel-eng trac instance.  They
> create the drpms.  The bugzilla component is for problems with the kernel
> itself.

I don't fina a Fedora component named rel-eng
Kindly suggest how to find it in the Component list


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