Bug 10511 - Request to have colord-kde-0.3.0-mga3 rpm in Mageia3
Summary: Request to have colord-kde-0.3.0-mga3 rpm in Mageia3
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: John Balcaen
QA Contact:
URL: http://rpm.pbone.net/index.php3?stat=...
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-06-12 19:29 CEST by kalagani kalagani
Modified: 2015-03-31 16:03 CEST (History)
3 users (show)

See Also:
Source RPM: colord-kde
CVE:
Status comment:

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

Description kalagani kalagani 2013-06-12 19:29:41 CEST 
Description of problem:
It 's not really a problem but a request for enhancement.
Visiting Linux meeting near Paris, I discovered on the KDE 'stand the feature
colord-kde was existing in the KDE4.10.
So, Mageia3 is coming with KDE4.10 but not the colord-kde package.



Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-06-12 23:04:00 CEST

Keywords: (none) => Triaged
CC: (none) => lmenut, nicolas.lecureuil
Assignee: bugsquad => balcaen.john
Source RPM: colord-kde-0.3.0-mga3 or colord-kde-0.2.0-mga3 is missing in Mageia3 while existing in Mageia4 => colord-kde

Adrien D 2013-06-24 23:32:11 CEST

CC: (none) => adrien_d

Comment 1 Marja Van Waes 2015-03-31 16:03:54 CEST 
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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