Comment #56 on issue 1635 by colinpkc...@gmail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Apart from using lily-dev, now that lilyo-net is back on the air, the
instructions in CG 4.2 worked well for me on my Ubuntu machines.
Comment #55 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I've just ordered a new PC which I'm going to install Ubuntu onto, and I'm
planning to use these instructions:
http://lilypond.org
Comment #54 on issue 1635 by paconet@gmail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
What required program are you asked to install? if it is fontforge, I run
Ubuntu and had the same problem. Uninstall fontforge, compile
Comment #53 on issue 1635 by brownian.box: clean up misleading warnings in
website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I am running ubuntu linux. Well, I did not try to get it working yet. Thank
you, I feel like I'll ask you for some help, if I fail to get it worki
Comment #52 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
What system are you running?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://
Updates:
Status: Verified
Comment #51 on issue 1635 by brownian.box: clean up misleading warnings in
website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Yes, I have an up to date git, but I can not pass configure stage, I've
got "please install required programs".
Comment #50 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Sorry, Dmytro, it was done ages ago and I don't have a record. If you have
an up to date git, run "make website" and if you have no
Comment #49 on issue 1635 by brownian.box: clean up misleading warnings in
website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Please, which commit ID?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mail
Updates:
Status: Fixed
Comment #48 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Fixed in current git.
___
bug-lilypond mailing list
bug-l
Comment #47 on issue 1635 by colinpkc...@gmail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Sounds good to me, Phil. The new issue could become one of making language
handling consistent across all components of the (refurbished
Comment #46 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I think this is fixed. However, there are a number of references
to "English only build" which I've clearly not tackled. I think t
Comment #45 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
a patch directly is fine.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.or
Comment #44 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
OK. Done. I've also made a couple of minor changes to prevent the double
slashes in, for example, Documentation//changes. The doub
Comment #43 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Nah, just put a
docs-without-directories = ['changes', 'music-glossary']
at the top of the source file. Don't mess around with separate text
Comment #42 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I was working down the road of adding the known missing directories to the
list of known missing files, and then not printing the wa
Comment #41 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Let's just remove (or comment out) the error. Or, just to be totally
ultra-safe, dump a hard-coded list of files without directories:
- cha
Comment #40 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
They come from extract_texi_filenames.py. It seems to assume that every
filename supplied to it also has an associated directory -
Updates:
Labels: -Patch-review
Comment #39 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
thanks, patch pushed.
One thing left to clean up:
NOT A DIR from: /main/src/lilypond/build
/home/gpe
Comment #38 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
... did I mention that my traveling companion, in addition to being old
enough to be my mother, actually works with my mother organizing a mu
Comment #37 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
According to my map, it's around Oude Kerk. If you found it, fine. What
did you buy :-)
http://codereview.appspot.com/4515042/
Comment #36 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Sorry, I'm lost. Figuratively and literally -- it took us over an hour to
find the red light district last night[1], despite having two maps
Comment #35 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
The problem I have with this approach is that it can be illuminating to see
the bibtex output and the extract*.py output, and it see
Comment #34 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I still think it would be too weird to hide the make commands with -s -- in
my experience, every project that uses automake prints such outpu
Comment #33 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
The make echos are about 50-60 lines long - longer than a default terminal
window, and so would cause a warning to scroll off the to
Comment #32 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I'd rather not use make -s. The command echos don't take up many lines,
and I think it would cause more problems than it would solve. The o
Comment #31 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
There's a make option (-s) that supresses "informative" echoing of its
commands, so it's not too hard to reduce some of the noise th
Updates:
Labels: Patch-review
Comment #30 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Patch on Rietveld and the only likely reviewer has given a LGTM. Please
push. Further work t
Comment #29 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I haven't done an exhaustive file-by-file check of why they don't exist,
but basically it's because there are links to them in the s
Comment #28 on issue 1635 by colinpkc...@gmail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Just applied the patch and ran make website. Certainly a *ton* cleaner and
feels much faster. Well done, Phil!
The burned-out alpha ge
Comment #27 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Just for initial interest, I ran make doc &> DocBuild.txt. The resulting
file is 30 megs and 536,364 lines long.
___
Comment #26 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Phil: ok, sounds like a plan. Maybe instead of having a --website flag, it
could instead be a --ok-missing-file=website-ok-missing.txt (nam
Comment #25 on issue 1635 by colinpkc...@gmail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
If we can be sure that make website has no external dependencies, i.e. as
Graham says, without ../configure, then I believe we can simply
Comment #24 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
No plans to do so at present. As for the "files that aren't there that we
know aren't there" I was just going to make a textfile, r
Comment #23 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
well, there already exists a
python/langdefs.py
Reasons I didn't use it for the website build (none of these good):
- I don't know how the f
Comment #22 on issue 1635 by colinpkc...@gmail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
The idea of a single file containing the list of required files, had also
occurred to me, and suggests a similar approach to issues 1004,
Comment #21 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I have no objection to that, but this is now in territory that somebody may
comment on in a patch -- exactly where should such a file go, how
Comment #20 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I can have a go at modding extract*.py to add the --website (or -w ?) flag
and suppress warnings. I can see the point of only doing
Comment #19 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
oops, ok. I was confused between "wind.itely" and "winds.itely". Hmm, it
would be nice if the auto-generated files from snippets were named
Comment #18 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Oh - and by the way, bibs only builds the bibliography files in others-did
and we-wrote, so changing the order by itself wouldn't ge
Comment #17 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
@comment 15 - I can only find winds.itely in build/out and it's put there
(I reckon) by a doc build. I've just nuked my build direc
Comment #16 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
@Colin in comment 10: I personally never trust debuggers; I always add
print
commands myself, and sometimes add a
sys.exit(1)
to cause the
Comment #15 on issue 1635 by percival.music.ca: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Could I suggest "(c) most of the files do exist, but aren't where
extract_texi is looking" ? I mean, we definitely have a "winds.itely" and
Comment #14 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Previous comment. I did, of course, mean I'm going with "(b) they're not
really there".
Comment #13 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Concerning whether (a) the files actually exist and the error message is
false, or (b) they're not really there, I'm going with (a).
Comment #12 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
OK - here's a proposal to get rid of just 3 warnings. I realise this isn't
the bulk, but it's come up as part of understanding what
Comment #11 on issue 1635 by philehol...@googlemail.com: clean up
misleading warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Here's the the output from the first few files flagged as not found:
extract_texi_filenames.py: Processing
/home/phil/lilypond-git/
Comment #10 on issue 1635 by colinpkc...@gmail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Just chiming in with a bit here, I've been trying to run extract_text*.py
in the debugger of Eric (a Python IDE), and setting a breakpoin
Comment #9 on issue 1635 by percival.music.ca: clean up misleading warnings
in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I took a quick look at this. It looks like extract_texi_filenames.py
creates the xref files, which are used to allow us to do things like
Comment #8 on issue 1635 by percival.music.ca: clean up misleading warnings
in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Depends what you mean by "as you're no doubt aware". I'm aware that the
message which is printed to screen claims that a file was not found.
Comment #7 on issue 1635 by philehol...@googlemail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
As you're no doubt aware, most of the warnings from extract*.py are about
files not found - so we've got 2 options: either not produc
Comment #6 on issue 1635 by percival.music.ca: clean up misleading warnings
in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
That seems reasonable.
Note that there's two very different problems here:
- how to build the English website.
- how to build the translated we
Comment #5 on issue 1635 by philehol...@googlemail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
There's (not surprisingly) lots of .html files - most of the website except
the docs does appear to be there. I'm starting to wonder
Comment #4 on issue 1635 by percival.music.ca: clean up misleading warnings
in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
It is correct that "make website" does not produce documentation. It is
correct that it generates files inside a directory called out-website
Comment #3 on issue 1635 by philehol...@googlemail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
This is the slightly truncated description from the file itself:
# Description:
# This script parses the .texi file given and creates
Comment #2 on issue 1635 by percival.music.ca: clean up misleading warnings
in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Given the number of warnings that extract_text_filenames.py produces, I'm
not certain that it's worth looking at this as a bib problem. Botto
Comment #1 on issue 1635 by philehol...@googlemail.com: clean up misleading
warnings in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I've been looking at this error message:
extract_texi_filenames.py: Processing
/home/phil/lilypond-git/Documentation//essay.tely
No
Status: Accepted
Owner:
CC: philehol...@googlemail.com, colinpkc...@gmail.com
Labels: Type-Build Priority-High Maintainability
New issue 1635 by percival.music.ca: clean up misleading warnings in
website build
http://code.google.com/p/lilypond/issues/detail?id=1635
Start with "make webs
57 matches
Mail list logo
