Am Dienstag, den 28.04.2020, 15:23 +0100 schrieb Phil Holmes:
> On my machine make website returns:
>
> Traceback (most recent call last):
> File "/media/IntelSSD/lilypond/lilypond-git/scripts/build/website_post.py",
> line 179, in
> lines = open(file).readlines()
> File "/usr/lib/python3.5/enco
On my machine make website returns:
Traceback (most recent call last):
File "/media/IntelSSD/lilypond/lilypond-git/scripts/build/website_post.py",
line 179, in
lines = open(file).readlines()
File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self
2017-03-26 21:08 GMT+02:00 Francisco Vila :
> Hello, I am having problems trying to build the website as if it were
> the first time; subsequent tries do work and the build finishes
> successfully.
>
> However, the options CPU_COUNT=1 and -j1 work well even at first time.
> The error seems to be he
Hello, I am having problems trying to build the website as if it were
the first time; subsequent tries do work and the build finishes
successfully.
However, the options CPU_COUNT=1 and -j1 work well even at first time.
The error seems to be here:
/usr/bin/python -tt
/home/fravd/source/lilypond/sc
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 cur
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
, the second reestablishes it.
Then push your new patch.
--
Phil Holmes
- Original Message -
From: "Paul"
To:
Sent: Saturday, September 24, 2016 2:02 PM
Subject: Re: Staging not merging with master - make website fails
H
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
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
On Sat, Aug 17, 2013 at 12:33:39PM +, julien.ri...@gmail.com wrote:
> I did not touch that part specifically because I do not want to break
> anything with the current machine that runs this build. Is there a
> python2 on the host machine where this command would normally be run?
> AFAIK the py
e run?
AFAIK the python2 alias is only installed if python3 is also installed
on the system, which might or might not be the case.
Cheers,
Julien
Description:
make website fails on platforms where python3 is the default.
Use the python found by ./configure to build the website.
Please review
When building with WEBSITE_ONLY_BUILD, $(PYTHON) will default to python
(as defined at the top of the file). We do that because we don't run
./configure on the web server.
I _think_ this will be safe enough, but it might be nice to change the
upper definition to $(PYTHON) = python2
https://cod
LGTM
https://codereview.appspot.com/12769043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
14 matches
Mail list logo
