Mixxx 2.2.1
- stefan_mixxx
- Posts: 4
- Joined: Sat May 11, 2019 6:25 pm
Mixxx 2.2.1
Hi
I was just able to install mixxx 2.2.0 im MX18.
I would like to see mixxx 2.2.1 or/and 2.1.8 in MX18.
https://www.mixxx.org/download/
How can the deb packages here be updated?
http://mxrepo.com/mx/testrepo/pool/test/m/mixxx/
I just discovered that mixxx 2.2.1 is now in Debian experimental:
https://tracker.debian.org/news/1038847 ... erimental/
does this help?
Is there a way to install it from there?
I was just able to install mixxx 2.2.0 im MX18.
I would like to see mixxx 2.2.1 or/and 2.1.8 in MX18.
https://www.mixxx.org/download/
How can the deb packages here be updated?
http://mxrepo.com/mx/testrepo/pool/test/m/mixxx/
I just discovered that mixxx 2.2.1 is now in Debian experimental:
https://tracker.debian.org/news/1038847 ... erimental/
does this help?
Is there a way to install it from there?
Re: Mixxx 2.2.1
It still depend on the... dependencies. Download it and click the deb, you will find out immediately if there are be problems on MX-18
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
- stefan_mixxx
- Posts: 4
- Joined: Sat May 11, 2019 6:25 pm
Re: Mixxx 2.2.1
thanks Jerry
I downloaded https://packages.debian.org/source/experimental/mixxx
and did:
Code: Select all
dpkg-source -x mixxx_2.2.1~dfsg-1.dsc
cd mixxx-2.2.1~dfsg/
debuild -b -uc -us
dpkg-buildpackage -rfakeroot -us -uc -b
dpkg-buildpackage: Information: Quellpaket mixxx
dpkg-buildpackage: Information: Quellversion 2.2.1~dfsg-1
dpkg-buildpackage: Information: Quelldistribution experimental
dpkg-buildpackage: Information: Quelle geändert durch Matteo F. Vescovi <mfv@debian.org>
dpkg-source --before-build mixxx-2.2.1~dfsg
dpkg-buildpackage: Information: Host-Architektur amd64
dpkg-checkbuilddeps: Fehler: Nicht erfüllte Bauabhängigkeiten: chrpath debhelper (>= 11~) gir1.2-rsvg-2.0 libavcodec-dev libavformat-dev libebur128-dev libexpat-dev libfftw3-dev libgl1-mesa-dev libglu1-mesa-dev liblilv-dev libqt5opengl5-dev libqt5svg5-dev libqt5x11extras5-dev libqt5xmlpatterns5-dev libsoundtouch-dev (>= 2.0.0) libupower-glib-dev qtscript5-dev scour
dpkg-buildpackage: Warnung: Bauabhängigkeiten/-konflikte nicht erfüllt; Abbruch
dpkg-buildpackage: Warnung: (Verwenden Sie -d, um sich darüber hinwegzusetzen.)
debuild: fatal error at line 1116:
dpkg-buildpackage -rfakeroot -us -uc -b failed
Code: Select all
debhelper (>= 11~)
Code: Select all
libsoundtouch-dev (>= 2.0.0)
Re: Mixxx 2.2.1
I think, it was meant to download the deb package not the source.stefan_mixxx wrote: ↑Sat May 11, 2019 7:24 pm I downloaded https://packages.debian.org/source/experimental/mixxx
and did:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Mixxx 2.2.1
Dependencies are usually quite different depending on what platform the program was compiled on. Since we can build 2.2.0, odds are that 2.2.1 will not be a problem.
We have debhelper 12 in the main MX 17/18 repo, so the problem with that is that it wasn't installed.
Soundtouch 2.1.2 is in the test repos, that's what I used to build Mixxx 2.2.0.
We have debhelper 12 in the main MX 17/18 repo, so the problem with that is that it wasn't installed.
Soundtouch 2.1.2 is in the test repos, that's what I used to build Mixxx 2.2.0.
- stefan_mixxx
- Posts: 4
- Joined: Sat May 11, 2019 6:25 pm
Re: Mixxx 2.2.1
Ok
I got debhelper and libsoundtouch from the testrepo:
http://mxrepo.com/mx/testrepo/pool/test ... 15_all.deb
http://mxrepo.com/mx/testrepo/pool/test ... _amd64.deb
now "libprotobuflite17" is missing which I got from
http://ftp.de.debian.org/debian/pool/ma ... _amd64.deb
but's there are more and more dependencies...
now libqt5core5a is missing.
I am wondering if there is a better way to automatically resolve dependencies and also get future mixxx releases directly compatible with mx Linux?
Maybe I have to look deeper in how deb packaging works, any hits where to start reading?
I got debhelper and libsoundtouch from the testrepo:
http://mxrepo.com/mx/testrepo/pool/test ... 15_all.deb
http://mxrepo.com/mx/testrepo/pool/test ... _amd64.deb
now "libprotobuflite17" is missing which I got from
http://ftp.de.debian.org/debian/pool/ma ... _amd64.deb
but's there are more and more dependencies...
now libqt5core5a is missing.
I am wondering if there is a better way to automatically resolve dependencies and also get future mixxx releases directly compatible with mx Linux?
Maybe I have to look deeper in how deb packaging works, any hits where to start reading?
Re: Mixxx 2.2.1
Debs from upstream are not going to be compatible. That's why we rebuild them from the source on our base.
For what it's worth, I've just built packages of 2.2.1 for MX 17-18. Here's what I changed:
Debhelper version is set in debian/control and debian/compat.
Disabling the dbgsym packages is optional. Here's what the build-depends look like now:
For the Jessie-based builds, I have to add alternatives for their versions of the libvamp build-depends. I just copy what I already did for the 2.2.0 build in our test repo.
The same code with the alternatives builds on Jessie, Stretch, and upstream without any changes, though. That's what I'll do when I put Mixxx 2.2.1 in my OBS multimedia repo, so I only have to upload one set of sources--it's more flexible.
For what it's worth, I've just built packages of 2.2.1 for MX 17-18. Here's what I changed:
Code: Select all
* Add python-scour as alternate build-depend to scour.
* Drop to debhelper 10 compat to ease backports.
* Disable automatic dbgsym packages.
Disabling the dbgsym packages is optional. Here's what the build-depends look like now:
Code: Select all
Build-Depends:
chrpath,
debhelper (>= 10),
docbook-to-man,
gir1.2-rsvg-2.0,
libavcodec-dev,
libavformat-dev,
libchromaprint-dev,
libebur128-dev,
libexpat-dev,
libfftw3-dev,
libflac-dev,
libgl1-mesa-dev,
libgles2-mesa-dev [armel armhf], #don't apply for MX
libglu1-mesa-dev,
libhidapi-dev (>= 0.8.0~rc1),
libid3tag0-dev,
libjack-dev,
liblilv-dev,
libmad0-dev,
libogg-dev,
libopus-dev,
libopusfile-dev,
libportmidi-dev [linux-any],
libprotobuf-dev,
libqt5opengl5-dev,
libqt5svg5-dev,
libqt5x11extras5-dev,
libqt5xmlpatterns5-dev,
librubberband-dev,
libshout-dev,
libsndfile1-dev,
libsoundtouch-dev (>= 2.0.0),
libsqlite3-dev,
libtag1-dev,
libupower-glib-dev,
libusb-1.0-0-dev,
libvamp-hostsdk3v5,
libvamp-sdk2v5,
libvorbis-dev,
pkg-config,
portaudio19-dev,
protobuf-compiler,
qtscript5-dev,
scons,
scour | python-scour,
vamp-plugin-sdk
Code: Select all
libvamp-hostsdk3v5 | libvamp-hostsdk3,
libvamp-sdk2v5 | libvamp-sdk2,
Re: Mixxx 2.2.1
The Debian wiki does have a simple backporting guide, and we have a more complex one in our wiki. However, Mixxx is a little more complicated because some of the build-depends changed names upstream, and the maintainer didn't use alternatives like we did. It's just my choice to make it easier to backport. Debhelper 10 is fine now for most builds, but there are some packaging commands that do require a newer version.Maybe I have to look deeper in how deb packaging works, any hits where to start reading?
But you can always ask backporting questions here, too...probably in the community repo section. Most of our package builds are now done in generic Debian schroots using pbuilder, some in schroots using sbuild if pbuilders fail, or in Virtual Box VM's if those fail (like for openjdk-8 that I just did for MX 15).
- stefan_mixxx
- Posts: 4
- Joined: Sat May 11, 2019 6:25 pm
Re: Mixxx 2.2.1
thank you very much @Stevo