On 09/24/2016 12:55 PM, Phil Holmes wrote:
And by the wonder that is the website build, you'll see that
lilypond.org is already showing the new front page.
Indeed! Very nice.
One problem... the news page is redirecting to the home page because the
htaccess file here:
Documentation/web/s
- Original Message -
From: "Paul"
To: "Phil Holmes" ;
Sent: Saturday, September 24, 2016 3:23 PM
Subject: Re: Staging not merging with master - make website fails
On 09/24/2016 09:56 AM, Phil Holmes wrote:
I think you will definitely have to back out the current commit, add the
ima
>> https://bugs.freedesktop.org/show_bug.cgi?id=97546
>>
>> The proposed fix hasn't been applied yet to the fontconfig git
>> repository – maybe we should downgrade GUB's fontconfig version to
>> 2.12.0 until this is fixed.
>
> I think that there is another possible solution. To use the
> prop
>> Most likely cause of the issue will be the 2.12.1 change that
>> improved cache validation logic (and for yet unknown reasons always
>> invalidates the cache of the Mac OS System fonts)
>>
>> https://www.freedesktop.org/software/fontconfig/release/ChangeLog-2.12.1
>
> Aah, this rings a bell.
>
On 09/24/2016 09:56 AM, Phil Holmes wrote:
I think you will definitely have to back out the current commit, add
the images and repush to staging. My notes on how to do this:
Thanks Phil! That worked. My new patch is now pushed to staging with
the images added (commit message is the same as
I think you will definitely have to back out the current commit, add the
images and repush to staging. My notes on how to do this:
Removing and recreating staging
---
First do something like
git fetch
git log -3 origin/staging
to be really, really sure what commit
> Most likely cause of the issue will be the 2.12.1 change that
> improved cache validation logic (and for yet unknown reasons always
> invalidates the cache of the Mac OS System fonts)
>
> https://www.freedesktop.org/software/fontconfig/release/ChangeLog-2.12.1
Aah, this rings a bell.
https:/
Hello James,
Thanks for your message. I was wondering what had gone wrong... What's
the best way to fix things from here? Should I back out my commit on
staging and redo the push with a new patch with images included? I'm
not sure how to back out a commit on a remote branch... Locally I wo
Discovered already that indeed a newer version of font-config is packaged with
2.19.47 (2.12.1 versus 2.11.95).
Most likely cause of the issue will be the 2.12.1 change that improved cache
validation logic (and for yet unknown reasons always invalidates the cache of
the Mac OS System fonts)
ht
Looked a bit furher into this, and seems to be an issue of the fontconfig
library. Was that upgraded between the binaries of 2.19.46 and 2.19.47?
Seems that in Lilypond 2.19.47 fontconfig is no longer having a cache/dir
checksum match for the system font library and thus rescans it on each run t
Hello,
commit29941d96aa9942cfe914440b90b49ff7e015742e
>From Paul is missing its image files - they have been uploaded into
LilyPond Extra but need to be included in this commit in staging.
Regards
--
--
James
___
lilypond-devel mailing list
li
Meanwhile, I have compiled make 3.82 and made it available before make
4.0 in the PATH. Then the process goes further up to this point:
$ bin/gub --verbose darwin-x86::cross/gcc
...
building package: linux-x86::cross/gcc
*** Stage: download (cross/gcc, linux-x86)
*** Stage: untar (cross/gcc, lin
>> Then some downloads and later it came to this error saying make is too old:
>>
>> Tail of target/linux-x86/log/glibc-core.log
>> checking for gnumsgfmt... no
>> checking for gmsgfmt... no
>> checking for msgfmt... msgfmt
>> checking version of msgfmt... 0.19.2, ok
>>
13 matches
Mail list logo
