Graham Percival <gra...@percival-music.ca> writes:
> can somebody fix this? and depending on dak, either push directly
> to master (which means he has to play yet more games with
> dev/staging),
dev/staging is in a reasonably calm state right now and would be easy to
rebase. But what's the advantage?
> or push to dev/staging and then wait for James to do his stuff and
> then I'll try making 2.15.17 again then.
>
>
> file from VC not distributed:
> lilypond-2.15.17/Documentation/fr/texidocs/alternative-breve-note.texidocs
> rm -rf /tmp/tmpz2NH5N
> Traceback (most recent call last):
> File "test-lily/dist-check.py", line 137, in <module>
> main ()
> File "test-lily/dist-check.py", line 132, in main
> check_files (tarball, repo)
> File "test-lily/dist-check.py", line 117, in check_files
> raise Exception ('dist error found')
> Exception: dist error found
> make[3]: *** [unlocked-dist-check] Error 1
> make[3]: Leaving directory `/main/src/gub'
> make[2]: *** [cached-dist-check] Error 2
> make[2]: Leaving directory `/main/src/gub'
> make[1]: *** [dist-check] Error 2
> make[1]: Leaving directory `/main/src/gub'
> make: *** [lilypond] Error 2
A positive nuisance. Blocked patches keep piling up in my queue.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
