This is obsolete, closing this.
** Changed in: mixxx
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804513
Title:
Cosmic: Mixxx 2.1.3 is not stable with Qt5
Any updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804513
Title:
Cosmic: Mixxx 2.1.3 is not stable with Qt5
To manage notifications about this bug go to:
Done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804513
Title:
Cosmic: Mixxx 2.1.3 is not stable with Qt5
To manage notifications about this bug go to:
> The issues mentioned to be caused by the 'buggy' version do seem to be
high-impact, but from what I understand the application is still usable
- is that correct?
It depends on the definition of usable. You can start the application
play tracks, but it may stop a party, which is the most
Thanks again for actively working on this! I'd certainly like Robie to
take a look at this upload as he was the one originally involved in
handling the SRU. But a few of my second-opinion cents here.
With my SRU hat on, it's very difficult handling such huge new upstream release
updates to our
The cosmic package is still 2.1.3~dfsg-1
What can I do to make progress here?
@Robie Basak: can you have a look?
** Changed in: mixxx
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Uploaded to the queue, it's up to the SRU team now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804513
Title:
Cosmic: Mixxx 2.1.3 is not stable with Qt5
To manage notifications about this bug
Thank you very much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804513
Title:
Cosmic: Mixxx 2.1.3 is not stable with Qt5
To manage notifications about this bug go to:
I'll upload this on Monday.
** Also affects: mixxx (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: mixxx (Ubuntu)
Status: New => Fix Released
** Changed in: mixxx (Ubuntu)
Importance: Undecided => High
** Changed in: mixxx (Ubuntu Cosmic)
Importance:
I have tried to improve the initial post. Is it OK like that?
** Description changed:
- [Impact]
-
- * Mixxx 2.1.3 builds with Qt5 but the support is experimental. The
-resulting binary is untested and suffering bugs.
+ [Impact]
- * We as Mixxx team do not support 2.1.x qt5 builds.
We have a quite good experience with 2.2.0 on Linux since the release,
no QT unrelated regressions.
We have some regressions tracked here
https://launchpad.net/mixxx/+milestone/2.2.1 due to QT5 though.
The current Cosmic version already suffers these issues.
--
You received this bug
Mixxx doesn't follow a stable/unstable release process. All mixxx
releases are considered stable and we recommend users always upgrade to
the latest version. Any release may introduce new bugs, but many more
are also fixed. We do offer point releases for a limited amount of time
to address
Your bug description is a really good start, but I have a few more
questions before we can proceed with this.
The goal from here is to identify problems with the update that may
arise. I will admit to not being intimately familiar with Mixxx, but the
idea is to not add any bugs in the process. If
I have update the initial post with all the requested info so far. Is
anything missing?
The mayor argument is that the currently released version has bypassed
all quality checks of the Mixxx community.
The outstanding issue among others is the leak if GUI responds and possible
freezes.
> Thank you Robert for you explainations. I appreciate you efforts to
keep Ubuntu as stable as possible.
Thanks, and likewise I appreciate you caring for the user experience of
this package in Ubuntu.
> I there anything left to do for me here?
I think there are a bunch of outstanding questions
Thank you Robert for you explainations. I appreciate you efforts to keep
Ubuntu as stable as possible.
However this case is special. You can't not treat the current repository
version as stable. It is basically a untested 2.2 alpha with a wrong
version number, that slipped into the Debian repros
> Solutions would be to go to a 2.1.3 Qt4 build a 2.1.7 Qt4 build or a
2.2.0 Qt5 build.
Sorry, I missed your 2.1.x proposals earlier. My previous comments is
referring only to the 2.2.x proposal. For 2.1.x, please see the document
Simon linked for details of the policy (specifically
We can certainly consider this _if_ the current version in Cosmic really
is a problem for users that cannot practically be fixed any other way.
But please could you actually demonstrate that? For the only bug
actually linked, surely a cherry-pick would be lower regression risk for
existing users?
** Description changed:
- Mixxx 2.1.3 build with Qt but the support is experimental.
- The resulting binary is untested and suffering bugs.
- We as Mixxx team do not support 2.1.x qt5 builds. So the user is pretty alone
with issues with throws a bad light on Mixxx.
- Fist bugs are emerging
Thank you for taking care here.
> Part of this process involves ensuring that only bugfixes and patches
suitable for stable releases are accepted.
This rule does not apply here, the released binaries are unusable because it is
a Qt4 Version build with Qt5 and suffers MANY bugs. Here it is the
Hello, I was asked to take a look at this bug.
In Ubuntu, we have a Stable Release Update process which is in place to
ensure a smooth update process for our users:
https://wiki.ubuntu.com/StableReleaseUpdates
Part of this process involves ensuring that only bugfixes and patches suitable
for
Ping! This bug is still pending. Who can update the Mixxx package?
https://packages.ubuntu.com/cosmic/mixxx
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804513
Title:
Cosmic: Mixxx 2.1.3 is not
Ok, the Debian upstream packages are updated:
https://packages.debian.org/buster/mixxx
https://packages.debian.org/sid/mixxx
Who is responsible to fetch these changes for Ubuntu? It is really a bad
situation without this.
--
You received this bug notification because you are a member of Ubuntu
I have just emailed Matteo.
Is he also responsible for this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804513
Title:
Cosmic: Mixxx 2.1.3 is not stable with Qt5
To manage notifications
This package should be immediately updated to the latest stable release Mixxx
2.2.0
This is the first version that is stable with Qt5.
The package currently shipped with Cosmic is a untested alpha Version.
** Changed in: mixxx
Status: New => Confirmed
** Changed in: mixxx
Importance:
...one more reason to not revert the migration from Qt4 to Qt5 in 2.2.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804513
Title:
Cosmic: Mixxx 2.1.3 is not stable with Qt5
To manage
26 matches
Mail list logo
