So is the source code release in http://downloads.mixxx.org/mixxx-1.11.0/
stable now?
The issue is that I'd like to get an updated mixxx package onto rpmfusion.org,
and want to know if I can refer to that source release in the .spec file, e.g.
Source0:
Now that the release is out the door and we all have some breathing room, can I
get some opinions on my pending changes and blueprints?
https://bugs.launchpad.net/mixxx/+bug/1051106 is a simple implementation of an
incremental/pausable library-scan, to allow the locked-database problem during
Since I've done a little ffmpeg programming in the past, I thought I'd take a
look at this.
Hopefully I'm doing my comparison right; inside of a checkout of Mixxx's trunk,
I did bzr update -r 3365, since that seems to be the last version that was
merged into the ffmpeg branch.
Assuming my
Wait...it's easier than that...instead of having to fetch a QTextCodec, I can
just call QString::fromUtf8().
New patch. :-)
Steven Boswell
From: Steven Boswell II ulat...@yahoo.com
To: mixxx-devel@lists.sourceforge.net mixxx-devel@lists.sourceforge.net
Sent:
I agree only bug fixes should go in the 1.11.1 branch. String/GUI changes
make sense to delay.
We haven't looked too closely at 1.11.1, it's just a handy place to punt a
bug to when you know it isn't suitable for 1.11.0. Also we didn't have a
1.12.0 milestone created until recently so some bugs
The build problem I just ran into was reported on the forums; see
http://www.mixxx.org/forums/viewtopic.php?f=3t=4382 .
Unfortunately, no one ever answered him.
The problem is that the source code being built from wasn't part of a Bazaar
checkout, and src/SConscript doesn't handle that
Hello,
Thank you for trying this out! I'm in somekind of bzr merge limbo/hell. I
didn't get right what to merge first (I merged lp:mixxx/1.11) after that
someone remind me that correct merge should be lp:mixxx. After that I
merged from lp:mixxx but I didn't do as smooth I liked it to go..
I suck
