Bug 17428 - Backport Request: Mixxx 2.0
Summary: Backport Request: Mixxx 2.0
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL: http://www.mixxx.org/whats-new-in-mix...
Whiteboard: MGA5-64-OK MGA5-32-OK
Keywords: Backport
Depends on:
Blocks:
 
Reported: 2015-12-31 17:22 CET by Pavel Fric
Modified: 2016-03-27 00:29 CET (History)
3 users (show)

See Also:
Source RPM: mixxx
CVE:
Status comment:


Attachments

Description Pavel Fric 2015-12-31 17:22:14 CET
Version 2.0 of Mixxx DJ application was just released.

http://mixxxblog.blogspot.cz/2015/12/announcing-mixxx-20.html

Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-12-31 21:01:34 CET
That needs to be done in cauldron, first (it will then automatically end up in Mga6)

After it gets pushed to cauldron, you can reopen this report and ask for it to be backported for Mageia 5.

Our updates policy doesn't allow for a package to be updated in a stable release just for new features
https://wiki.mageia.org/en/Updates_policy#Version_Policy

However, there is a chance mixxx-2.0 could go in backports
https://wiki.mageia.org/en/Backports_policy

Assigning to all packagers, since there is no maintainer for Mixxx

CC: (none) => marja11
Version: 5 => Cauldron
Assignee: bugsquad => pkg-bugs

Comment 2 José Jorge 2016-01-01 12:41:24 CET
I will try to update that, sorry it will be too late for new years day

Status: NEW => ASSIGNED
CC: (none) => lists.jjorge

Comment 3 José Jorge 2016-01-02 12:20:09 CET
Mixxx 2 is now in Cauldron. Upstream says it is "crashy" with taglib 1.09 so it is not a good idea to backport it to MGA5.

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

Comment 4 José Jorge 2016-01-23 09:18:50 CET
(In reply to José Jorge from comment #3)
> Mixxx 2 is now in Cauldron. Upstream says it is "crashy" with taglib 1.09 so
> it is not a good idea to backport it to MGA5.

In fact, I have tried to backport it, played music for hours and got no crash.
The new features are very nice, so I think a backport is worth.

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

José Jorge 2016-01-23 09:19:12 CET

Summary: Mixxx 2.0 - request for updating of package => Backport Request: Mixxx 2.0

José Jorge 2016-01-23 09:20:48 CET

Keywords: (none) => Backport
Component: RPM Packages => Backports
Version: Cauldron => 5
Assignee: pkg-bugs => qa-bugs
Severity: normal => enhancement

Comment 5 José Jorge 2016-01-23 09:23:47 CET
The package Mixxx 2.0.0 was backported to MGA5. I will use it in both i586 and x86_64 systems for a few days, and report here.

RPM in core/backports_testing:
mixxx-2.0.0-1.mga5.{i586,x86_64}

SRPM in core/backports_testing:
mixxx-2.0.0-1.mga5.src
Comment 6 José Jorge 2016-01-24 15:30:31 CET
Tested Ok in i586, even if I had to launch it with --safemode as i915 driver lies about it's capablities. This is a known Intel bug on old hardware that says it is OpenGL 2.1 compliant while in fact it does not accept full length shaders :

https://bugs.launchpad.net/mixxx/+bug/1530180/comments/15

So I suggest changing slightly the advisory :

Mixxx 2.0.0 was backported to MGA5. As it uses now OpenGL 2.1, it triggers a bug on old Intel hardware, where the --safeMode workaround may help users.

Whiteboard: (none) => MGA5-32-OK

José Jorge 2016-01-29 08:25:02 CET

Whiteboard: MGA5-32-OK => MGA5-64-OK MGA5-32-OK

Comment 7 José Jorge 2016-01-29 08:27:52 CET
Tested with oldest i965 hardware (GMA3000) for 2 hours, all works nicely, so it is confirmed the need for --safeMode is only for Intel Gen3.
Comment 8 Thomas Backlund 2016-03-27 00:29:14 CET
Moved to backports

Status: REOPENED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED


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