Am 29.01.19 um 14:58 schrieb Knut Petersen:
On 29.01.19 14:30, Urs Liska wrote:
Looks like 64-bit Ubuntu, like my main machine. With an earlier
gub-version I had similiar problem, because of missing 32-bit
libraries.
I got further after installing:
lib32ncurses5
lib32z1
I suspect that
> The resulting installers all have SHA256 checksums different than the
> ones from Urs Liska's Nextcloud share.
Are you sure that the build refers to exactly the same lilypond git
commit as Urs's installers? HEAD is continuously updated...
> I don't know what's expected with that.
It would
On 1/29/2019 7:43 AM, Karlin High wrote:
Off and running again for now
Near as I can tell, the build succeeded. System specs given in an
earlier post. I forgot to use the "time" command, so I don't know
exactly how long it took. Going by logs, I'd say just under 10 hours.
Next time, I'll
Am Mi., 30. Jan. 2019 um 01:28 Uhr schrieb John Mandereau
:
>
> Hi Harm,
> Le mardi 29 janvier 2019 à 23:47 +0100, Thomas Morley a écrit :
> > Doing
> > $ chromium-browser gub/uploads/webdoc/v2.21.0/index.html
> > None of the tested links seem to work.
> >
> > But for
> > $ chromium-browser
Hi Harm,
Le mardi 29 janvier 2019 à 23:47 +0100, Thomas Morley a écrit :
> Doing
> $ chromium-browser gub/uploads/webdoc/v2.21.0/index.html
> None of the tested links seem to work.
>
> But for
> $ chromium-browser gub/uploads/localdoc/v2.21.0/index.html
> all links seem to work.
>
> No clue
Am Di., 29. Jan. 2019 um 23:08 Uhr schrieb Thomas Morley
:
>
> Am Mo., 28. Jan. 2019 um 13:53 Uhr schrieb Knut Petersen
> :
> >
> > Hi everybody!
> >
> > I created a branch in my gub repository that contains
> > https://github.com/gperciva plus pull requests 53-60. Therefore it is
> > pretty
Am Mo., 28. Jan. 2019 um 13:53 Uhr schrieb Knut Petersen
:
>
> Hi everybody!
>
> I created a branch in my gub repository that contains
> https://github.com/gperciva plus pull requests 53-60. Therefore it is pretty
> easy to test if that version of gub succeeds to build current lilypond master
On Tue 29 Jan 2019 at 10:19:33 (+0100), Knut Petersen wrote:
> Hi everybody
>
> Urs Liska provides installers for branch master of lilypond, generated by an
> updated version of our build system GUB:
>
>https://cloud.ursliska.de/s/QPINwLqJNeVslCu
>
> There you'll find
>
>
On Tue 29 Jan 2019 at 13:56:00 (-0600), David Wright wrote:
> On Tue 29 Jan 2019 at 10:19:33 (+0100), Knut Petersen wrote:
> > Hi everybody
> >
> > Urs Liska provides installers for branch master of lilypond, generated by
> > an updated version of our build system GUB:
> >
> >
On 2019/01/29 17:23:01, nhoc1990q1 wrote:
On 2019/01/13 02:37:05, 浪漫 Joachim Metz的老婆 wrote:
> https://photos.app.goo.gl/KCakjdAeKg6WSURT7%3Cfont%3E%3C/font%3E
>
> vợ tôi
>
>
https://codereview.appspot.com/349090043/diff/20001/scripts/build/output-distance.py%3Cfont%3E%3C/font%3E%3Cfont
On 2019/01/13 02:37:05, 浪漫 Joachim Metz的老婆 wrote:
https://photos.app.goo.gl/KCakjdAeKg6WSURT7
style="vertical-align: inherit;">
vợ tôi
https://codereview.appspot.com/349090043/diff/20001/scripts/build/output-distance.py
Tập lệnh tập tin / build / output-distance.py
(trái):
Am 29.01.2019 um 10:19 schrieb Knut Petersen:
lilypond-2.21.0-1.linux-64.sh
Works fine, Ubuntu 18.04.1 LTS, Kernel 4.15.0-36-generic running as
guest in VirtualBox 5.2.22 r126460, host Windows 10 Version 1803.
lilypond-2.21.0-1.mingw.exe
Works fine too, Windows 10 Version 1803.
On 1/29/19 1:24 PM, David Kastrup wrote:
Paul Morris writes:
On 1/29/19 4:19 AM, Knut Petersen wrote:
lilypond-2.21.0-1.linux-64.sh
Installed on Ubuntu 18.04.1 LTS and tested with a couple of
pieces. Everything appears to be working fine.
Thanks to all for the work on GUB and the next
> On 29 Jan 2019, at 20:00, Urs Liska wrote:
>
> If you use alternative notation fonts you have to "install" them for every
> new LilyPond installation.
On MacOS it used used to work installing as a system font, and then only once
is required. Tried with Bravura.otf.
Am 29. Januar 2019 19:47:07 MEZ schrieb Michael Hendry
:
>> On 29 Jan 2019, at 09:19, Knut Petersen
>wrote:
>>
>> Hi everybody
>>
>> Urs Liska provides installers for branch master of lilypond,
>generated by an updated version of our build system GUB:
>>
> On 29 Jan 2019, at 09:19, Knut Petersen wrote:
>
> Hi everybody
>
> Urs Liska provides installers for branch master of lilypond, generated by an
> updated version of our build system GUB:
> https://cloud.ursliska.de/s/QPINwLqJNeVslCu
> There you'll find
> lilypond-2.21.0-1.darwin-ppc.tar.bz2
> On 29 Jan 2019, at 09:19, Knut Petersen wrote:
>
> Hi everybody
>
> Urs Liska provides installers for branch master of lilypond, generated by an
> updated version of our build system GUB:
> https://cloud.ursliska.de/s/QPINwLqJNeVslCu
> There you'll find
> lilypond-2.21.0-1.darwin-ppc.tar.bz2
Paul Morris writes:
> On 1/29/19 4:19 AM, Knut Petersen wrote:
>
>> lilypond-2.21.0-1.linux-64.sh
>
> Installed on Ubuntu 18.04.1 LTS and tested with a couple of
> pieces. Everything appears to be working fine.
>
> Thanks to all for the work on GUB and the next stable LilyPond release!
Well,
On 1/29/19 4:19 AM, Knut Petersen wrote:
lilypond-2.21.0-1.linux-64.sh
Installed on Ubuntu 18.04.1 LTS and tested with a couple of pieces.
Everything appears to be working fine.
Thanks to all for the work on GUB and the next stable LilyPond release!
-Paul
On Tue, Jan 29, 2019 at 8:25 AM Phil Holmes wrote:
>
> Could someone pint me to what I
> need to do in order to get the gub git stash up to date and correct?
Lots of things happening with GUB lately. Major discussion threads include:
"I cannot run make check since Issue 5450: relocate.cc:
On 2019/01/28 21:53:04, dak wrote:
On 2019/01/28 20:02:53, Valentin Villenave wrote:
> I can’t figure out how to make it work without resetting the
EventChord’s
> elements list. How would you proceed?
Without any pointer to what you are having problems with, this is
essentially
"do it
>> What I want to know, however, is the `significance threshold' such
>> courtesy messages should have.
>
> Pretty much any commit you are about to push to staging. It's as
> simple as that.
OK, deal.
Werner
___
lilypond-devel mailing list
[snip]
Please note that I've been out of the country for the last 3 weeks or so and
haven't been following all the gub threads. Could someone pint me to what I
need to do in order to get the gub git stash up to date and correct?
FWIW I did get gub running just before I went away by dint of
Hello,
Here is the current patch countdown list. The next countdown will be on
the February 1st
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push: No patches to push at this time.
Countdown:
5467 Fix make
On 29.01.19 14:30, Urs Liska wrote:
Looks like 64-bit Ubuntu, like my main machine. With an earlier
gub-version I had similiar problem, because of missing 32-bit
libraries.
I got further after installing:
lib32ncurses5
lib32z1
I suspect that
apt-get install libc6-dev-i386
fixes the
Il giorno mar 29 gen 2019 alle 14:28, Knut Petersen
ha scritto:
On 29.01.19 11:56, Thomas Morley wrote:
Am Di., 29. Jan. 2019 um 00:53 Uhr schrieb Karlin High
mailto:karlinh...@gmail.com>>:
On 1/28/2019 6:53 AM, Knut Petersen wrote:
Please report success / fails with os / version / cpu
Am 29.01.19 um 14:28 schrieb Knut Petersen:
On 29.01.19 11:56, Thomas Morley wrote:
Am Di., 29. Jan. 2019 um 00:53 Uhr schrieb Karlin High:
On 1/28/2019 6:53 AM, Knut Petersen wrote:
Please report success / fails with os / version / cpu info.
I really like the simple instructions you
On 1/28/2019 11:28 PM, Federico Bruni wrote:
More likely a download went wrong and the tar.gz file is not really a
tar.gz file.
/Gerade da ist das Problem./
It turns out that my gateway antivirus (Untangle, ClamAV I think)
doesn't like the odcctools file. The download had returned an HTML
On 29.01.19 11:56, Thomas Morley wrote:
Am Di., 29. Jan. 2019 um 00:53 Uhr schrieb Karlin High :
On 1/28/2019 6:53 AM, Knut Petersen wrote:
Please report success / fails with os / version / cpu info.
I really like the simple instructions you posted, Knut. I wouldn't be
testing Gub without
Werner LEMBERG writes:
>>> Formatting only. No change in behaviour.
>>
>> And grammar and wording changes in the comments and changes from ##
>> comments to # comments (which does not appear to make a difference
>> to Emacs though as opposed to comments in some other languages).
>
> Yes. `#'
I reverted pull request #59 on a local branch of gub. In the local
lilypond repository I created branch 3538700043 pointing to HEAD of
stable/2.20, and added the proposed patch to branch 353870043.
make LILYPOND_REPO_URL=git://golem/lilypond.git
LILYPOND_BRANCH=stable/2.20 lilypond
On 1/29/2019 3:19 AM, Knut Petersen wrote:
lilypond-2.21.0-1.darwin-x86.tar.bz2
Works on MacBook Air (mid 2012) with Intel Core i5 and macOS Mojave 10.14.2
--
Karlin High
Missouri, USA
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Knut Petersen wrote 29/01/2019 09:19:33
Urs Liska provides installers for branch master of lilypond, generated by an
updated version of our build system GUB:
https://cloud.ursliska.de/s/QPINwLqJNeVslCu
There you'll find
lilypond-2.21.0-1.darwin-ppc.tar.bz2
Hello,
On Tue, 29 Jan 2019 08:07:58 +0100 (CET), Werner LEMBERG wrote:
>
> >> Formatting only. No change in behaviour.
> >
> > And grammar and wording changes in the comments and changes from ##
> > comments to # comments (which does not appear to make a difference
> > to Emacs though as
Obviously filenames (STRACE/TP) will differ as they indicate the ID of
the processes.
Please send me those two files and target/darwin-ppc/log/odcctools.log.
Which two files, the tar and gzip files in .../usr/bin?
No, target/darwin-ppc/log/odcctools.log and the two files STRACE/TP
Am Di., 29. Jan. 2019 um 00:53 Uhr schrieb Karlin High :
>
> On 1/28/2019 6:53 AM, Knut Petersen wrote:
> > Please report success / fails with os / version / cpu info.
>
> I really like the simple instructions you posted, Knut. I wouldn't be
> testing Gub without them. My setup doesn't like the
>
Hi Knut,
as said I ran the GUB build on my Debian server as well.
Am 29.01.19 um 08:11 schrieb Knut Petersen:
On 29.01.19 00:53, Karlin High wrote:
*** Failed target: darwin-ppc::odcctools
gub.make:63: recipe for target 'packages' failed
make[1]: *** [packages] Error 1
make[1]: Leaving
On Tue, Jan 29, 2019 at 3:20 AM Knut Petersen wrote:
> lilypond-2.21.0-1.mingw.exe
Seems to work on Windows 10 Pro 64-bit version 1803.
And it's definitely LilyPond 2.21 because it choked on \partcombine
and needed \partCombine instead. Fixed with convert-ly.
--
Karlin High
Missouri, USA
Il giorno mar 29 gen 2019 alle 7:41, Urs Liska
ha scritto:
So what can I do to check whether make lilypond succeeded or failed?
Good question.
On Ubuntu 16.04...
I just found out that I managed to build the packages on 23rd of
January,
despite the errors I reported last week:
$ ls -lh
Hi everybody
Urs Liska provides installers for branch master of lilypond, generated by an
updated version of our build system GUB:
https://cloud.ursliska.de/s/QPINwLqJNeVslCu
There you'll find
lilypond-2.21.0-1.darwin-ppc.tar.bz2
lilypond-2.21.0-1.darwin-x86.tar.bz2
Hi Knut,
Am 29.01.19 um 10:02 schrieb Knut Petersen:
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
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
Am 29.01.19 um 08:32 schrieb Werner LEMBERG:
If we get more success reports, the resulting packages should be
uploaded so that other people not running gub can test them.
Developers can then have a look how to add support for 64bit
binaries on MacOS and Windows. Especially the former is
43 matches
Mail list logo
