| Summary: | Backport Request: Mixxx 2.0 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Pavel Fric <pavelfric> |
| Component: | Backports | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | lists.jjorge, marja11, tmb |
| Version: | 5 | Keywords: | Backport |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.mixxx.org/whats-new-in-mixxx-2-0/ | ||
| Whiteboard: | MGA5-64-OK MGA5-32-OK | ||
| Source RPM: | mixxx | CVE: | |
| Status comment: | |||
|
Description
Pavel Fric
2015-12-31 17:22:14 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 I will try to update that, sorry it will be too late for new years day Status:
NEW =>
ASSIGNED 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 (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
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 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
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 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. Moved to backports Status:
REOPENED =>
RESOLVED |