Bug 24928 - mixxx: update to 2.2.1
Summary: mixxx: update to 2.2.1
Status: RESOLVED DUPLICATE of bug 24969
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL: https://github.com/mixxxdj/mixxx/rele...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-06 08:21 CEST by kunda 1
Modified: 2019-07-03 21:27 CEST (History)
3 users (show)

See Also:
Source RPM: https://madb.mageia.org/rpm/show/source/1/application/0/release/cauldron/name/mixxx-2.2.0-2.mga7.src.rpm/arch/i586/t_media/3
CVE:
Status comment:

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

Description kunda 1 2019-06-06 08:21:09 CEST 
2.2.1 is latest stable
https://github.com/mixxxdj/mixxx/releases/tag/release-2.2.1
Comment 1 Lewis Smith 2019-06-06 09:07:45 CEST 
Not sure whether we automatically offer the latest version of individual applications. But if this is possible for M7, so much the better.

Assignee: bugsquad => lists.jjorge
CC: (none) => lewyssmith

Comment 2 David GEIGER 2019-06-06 12:49:34 CEST 
As we have already reply in others bugs we are now in "Release Freeze" so we do not update any packages anymore! So please it is not needed to file a new bug every new updated packages! 

thanks for your understanding!

CC: (none) => geiger.david68210

Comment 3 José Jorge 2019-06-06 17:51:13 CEST 
(In reply to David GEIGER from comment #2)
> thanks for your understanding!

Take it easy. I will provide an update for MGA7 as a backport, so that we don't break anything in the excellent 2.0 version ;-)

Expect at least one month before this happens. And bug me if I forget ;-)

Status: NEW => ASSIGNED

Comment 4 José Jorge 2019-07-03 21:27:11 CEST 
Mixx 2.2.1 is being tested as update n duplicate bug.

*** This bug has been marked as a duplicate of bug 24969 ***

CC: (none) => lists.jjorge
Status: ASSIGNED => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.