Bug 15418 - Upgrade qmmp 0.7.2 to 0.8.3 in cauldron
Summary: Upgrade qmmp 0.7.2 to 0.8.3 in cauldron
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL: http://qmmp.ylsoftware.com/index.php
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-04 09:51 CET by seb vala
Modified: 2015-03-07 17:53 CET (History)
1 user (show)

See Also:
Source RPM: qmmp-0.7.2-6.mga5
CVE:
Status comment:


Attachments

Description seb vala 2015-03-04 09:51:43 CET
Description of problem:

Hello,
The latest version of qmmp in Cauldron is 0.7.2 released on 26/08/2013 (very old).
Is it possible to update in 0.8.3 (latest version) released on 01.05.2015 before the release of Mageia 5 please?
Changelog => http://qmmp.ylsoftware.com/view_news.php?offset=0
thank you very much


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


How reproducible:
No bug, just a very old version of this software

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 seb vala 2015-03-04 09:53:29 CET
its 05.01.2015 not 01.05.2015 :)
Rémi Verschelde 2015-03-04 22:59:52 CET

CC: (none) => remi
Assignee: bugsquad => remi

Comment 2 Rémi Verschelde 2015-03-04 23:20:10 CET
I've updated qmmp in our SVN repository, I'm now waiting for the package to be submitted (we are in release freeze, so new versions have to be approved first by release managers).
Comment 3 seb vala 2015-03-05 13:51:02 CET
(In reply to Rémi Verschelde from comment #2)
> I've updated qmmp in our SVN repository, I'm now waiting for the package to
> be submitted (we are in release freeze, so new versions have to be approved
> first by release managers).

Good! Thank you very much
Comment 4 seb vala 2015-03-07 17:53:34 CET
good work, it works perfectly

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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