Hi Urs!
So what can I do to check whether make lilypond succeeded or failed?
The last lines of the terminal output will look like:
make -f lilypond.make update-versions
To upload, run:
make lilypond-upload LILYPOND_BRANCH=master
LILYPOND_REPO_URL=git://git.sv.gnu.org/lilypond.git
**** nsis rule
python bin/gub tools::nsis
calculating dependencies
Checking for iconv ... /usr/bin/iconv
Checking for g++ ... /usr/bin/g++
Checking for gcc ... /usr/bin/gcc
must rebuild[tools]: system::gcc system::g++ system::iconv
*** Stage: pkg_install (cross/gcc-core, linux-x86)
cross/gcc conflicts with cross/gcc-core
non-core cross/gcc already installed
skipping request to install cross/gcc-core
cross/gcc-doc conflicts with cross/gcc-core
non-core cross/gcc already installed
skipping request to install cross/gcc-core
cross/gcc-runtime conflicts with cross/gcc-core
non-core cross/gcc already installed
skipping request to install cross/gcc-core
*** Stage: pkg_install (glibc-core, linux-x86)
glibc conflicts with glibc-core
non-core glibc already installed
skipping request to install glibc-core
glibc-doc conflicts with glibc-core
non-core glibc already installed
skipping request to install glibc-core
done
**** rest rule
**** all rule
**** Default rule
make[1]: Leaving directory `/home/knut/sources/gub'
if everything worked fine.
In uploads you see the generated installers, the documentation, test results
etc:
drwxr-xr-x 2 knut users 4096 29. Jan 08:56 signatures
drwxr-xr-x 4 knut users 4096 29. Jan 08:56 localdoc
drwxr-xr-x 4 knut users 4096 29. Jan 08:56 webdoc
-rw-r--r-- 1 knut users 137828875 29. Jan 08:56
lilypond-2.21.0-1.webdoc.tar.bz2
-rw-r--r-- 1 knut users 158089031 29. Jan 08:55
lilypond-2.21.0-1.documentation.tar.bz2
drwxr-xr-x 4 knut users 4096 29. Jan 08:34 webtest
-rw-r--r-- 1 knut users 18416327 29. Jan 08:31
lilypond-2.21.0-1.test-output.tar.bz2
-rw-r--r-- 1 knut users 17226394 29. Jan 08:28 lilypond-2.21.0.tar.gz
-rwxr-xr-x 1 knut users 31251820 29. Jan 08:27
lilypond-2.21.0-1.freebsd-64.sh
-rwxr-xr-x 1 knut users 28063129 29. Jan 08:27
lilypond-2.21.0-1.freebsd-x86.sh
-rwxr-xr-x 1 knut users 30586997 29. Jan 08:27
lilypond-2.21.0-1.linux-ppc.sh
-rwxr-xr-x 1 knut users 31375293 29. Jan 08:27 lilypond-2.21.0-1.linux-64.sh
-rw-r--r-- 1 knut users 34665510 29. Jan 08:26 lilypond-2.21.0-1.mingw.exe
-rw-r--r-- 1 knut users 26746205 29. Jan 08:25
lilypond-2.21.0-1.darwin-x86.tar.bz2
-rw-r--r-- 1 knut users 26611149 29. Jan 08:25
lilypond-2.21.0-1.darwin-ppc.tar.bz2
-rwxr-xr-x 1 knut users 31208955 29. Jan 08:24
lilypond-2.21.0-1.linux-x86.sh
If you reached that point everything went fine.
At least we hope that everything went fine.
When we will start to update relevant components like guile we will need a way
to test if the generated archives contain a working lilypond or garbage. I see
that you already thought about that by providing the generated files on your
cloud. Thanks you.
Knut
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
