Bug 24910 - dkms rpms have mga6 suffix
Summary: dkms rpms have mga6 suffix
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 24895
  Show dependency tree / graph
 
Reported: 2019-06-06 01:31 CEST by katnatek
Modified: 2019-06-10 22:22 CEST (History)
2 users (show)

See Also:
Source RPM: dkms-2.0.19-39.mga6
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description katnatek 2019-06-06 01:31:24 CEST 
Description of problem:

all the packages related with this src.rpm have mga6 suffix
that could make think you have outdated packages in your system

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
katnatek 2019-06-06 01:31:46 CEST

Blocks: (none) => 24895

Comment 1 Lewis Smith 2019-06-06 08:54:33 CEST 
Hope this is right for you, Thomas.

Assignee: bugsquad => tmb
CC: (none) => lewyssmith

Comment 2 Lewis Smith 2019-06-06 09:43:26 CEST 
Confirmed as per srcRPM via MCC.
Comment 3 Dave Hodgins 2019-06-09 22:35:59 CEST 
Escalating to release blocker as dkms packages are on the iso images.

Priority: Normal => release_blocker
CC: (none) => davidwhodgins

Comment 4 Thomas Backlund 2019-06-10 22:22:45 CEST 
Not really a release blocker as it's a noarch package that does not change during rebuild.

Anyway, it got stuck at mga6 when I started upgrading it, but forgot to finish it :/

So I've rolled it back to kmown  Mga6 level and rebuilt it for Mga7...

Priority: release_blocker => Normal
Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.