Nightly builds - linux

• Jan 11, 2015 - 00:59

The nightly builds for the last few days are corrupt on the downloads page, they are about 70 mb in size

http://prereleases.musescore.org/linux/nightly/


Comments

To the keepers/builders of the Nightlies - thank you for your efforts and believe me when I say that it is appreciated. I don't want to sound ungrateful but is there a way you can test the executables that you have uploaded in a sandbox/VM to see that they run OK?

To bodhi,zazen:
There are four ways to correct our faults: we can change through behaviour, we can change through understanding, we can change from the heart, we can build from source instead of relying on others to do the builds for us whilst trying to strip the debugging stuff out.

In reply to by underquark

You're right. Our binary should run «out of the box»

I do not know enough about compilation to solve alone. That should be a joint work between developers and uploaders (as me).

I understand that a binary needs some libraries to run. In Windows world the actual binaries available on a computer are known. In Linux world they are not the same on each computer. The collection of libraries on a given computer relies on which distribution (and which version), and which softwares (especially Qt) have been installed, and how they were installed....

But I understand that basic users of Linux wish to benefit of a straightforward installation.
One difficulty is that the compiler can't check if his/her compilation runs on other computer. Perhaps we should add some explanations in http://prereleases.musescore.org/linux/nightly/ about the necessity to have Qtsomenumber installed

In reply to by robert leleu

Hi Robert, let me know if I can be of assistance. I agree completely - each distro have a different set of packages (dependencies). Perhaps the best solution is to package .deb and / or .rpm . Packaging takes time , especially for nightly builds, it can, however, be automated.

Ubuntu - Launchpad (ppa)
Fedora - Koji

I can help get you a list of dependencies for each distro (ubuntu or fedora), help package either .deb or .rpm, and help with ppa or Koji.

I *probably* would not take much more work they you are already doing , both a ppa and koji do the actual build, you just maintain the control files.

If you want to test in a virtual machine I highly suggest Fedora 21 or Ubuntu 14.10 + as both distros have the necessary packages in the repositories. With previous versions, you will need to compile dependencies from source, which is probably something you do not want to do.

You run ./mscore -F and then search for the dependencies. Most of the dependencies are libqt5 5.3 +

Ubuntu 14.04 (trusty) has qt5.2 in the repositories, so you would need to manually install 5.3.
Ubuntu 14.10 (utopic) has qt5.3 in the repos

Fedora 21 has libqt 5.3 (not sure about previous versions)

Debian sid has libqt5 in the reops

I am sure arch has qt5, but unless you have some experience, perhaps arch is not the best option for testing in a VM.

Not sure about other distros

yum provides '*/lib-foo'

apt-cache search foo

Hope that helps ;)

In reply to by underquark

From your comments, I assume you know it does not matter where you compile the daily build.

If you wish to compile, you will need to manually install Qt5.3 first, as this is a dependency. On 14.04 this means manually compiling / installing the dependencies. On 14.10 and fedora 21 the -dev packages are in the repos, so install with apt-get or yum.

If people want to run the compiled musescore binary on Ubuntu 14.04 they will have to install qt5.3 (or higher) manually. Qt5.3 is not currently available in the Ubuntu repositories, backports, or a ppa. The qt5.3 package from 14.10 does not work if you manually install the 14.10 .deb on 14.04.

qt5.3 is in debian sid, but not stable.

If you want to create a ppa for musescore and 14.04, you would be wise to package Qt5.3 as well as musescore.

If you are wanting to run the nightly builds, it is easiest to run on a version of linux that has qt5.3 available.

You can get a list of the packages needed to run the compiled binary if you run it with the -F flag

./muscore -F

and then search the repos (yum provides or apt-cache search).

On fedora 21 I have:

qt5-qtbase.x86_64 5.4.0-2.fc21 @updates
qt5-qtbase-gui.x86_64 5.4.0-2.fc21 @updates
qt5-qtdeclarative.x86_64 5.4.0-1.fc21 @updates
qt5-qtlocation.x86_64 5.4.0-2.fc21 @updates
qt5-qtquick1.x86_64 5.4.0-1.fc21 @updates
qt5-qtscript.x86_64 5.4.0-1.fc21 @updates
qt5-qtsensors.x86_64 5.4.0-2.fc21 @updates
qt5-qtsvg.x86_64 5.4.0-1.fc21 @updates
qt5-qttools.x86_64 5.4.0-1.fc21 @updates
qt5-qttools-common.noarch 5.4.0-1.fc21 @updates
qt5-qttools-libs-designer.x86_64 5.4.0-1.fc21 @updates
qt5-qtwebkit.x86_64 5.4.0-1.fc21 @updates
qt5-qtx11extras.x86_64 5.4.0-1.fc21 @updates
qt5-qtxmlpatterns.x86_64 5.4.0-1.fc21 @updates

Older versions of Ubuntu are more difficult.

There is a ppa - https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/ppa

However, the maintainers of the ppa do not have 5.3 available for 12.04 .

The "problem" with running the nightly build is that you need qt5.3 or higher and qt5.3 is not packaged prior to Ubuntu 14.10 (12.04 and 12.04) and the 14.10 package (.deb) does not work on 14.10 or 12.04 if you manually install it. Same with debian stable.

So my advice to new users is to use Ubuntu 14.10 or Fedora 21.

Perhaps generate a list of packages to install on the nightly build page:

Distros
Ubuntu 14.10
Fedora 21
Arch
etc

Dependencies:

apt-get install {list}
yum install {list}
etc

To support musscore and make it "easy" requires packaging, a ppa or koji. Both will package qt5.x as well as other dependencies , you need to generate the control files and upload the source.

PPA - https://help.launchpad.net/Packaging/PPA

Koji - http://fedoraproject.org/wiki/Koji

as muscore is in the repositories, we could probably contact the Debian/Ubuntu and Fedora packagers as well, they would almost certainly help. I can try to put you in touch with the package maintainers if that would be of assistance. I also know how to package both .deb and .rpm well enough if that would be of assistance.

Do you still have an unanswered question? Please log in first to post your question.