Le 12/09/2020 à 13:28, Jean Abou Samra a écrit :

Hi,

Towards the end of the process, `make doc` outputs warnings coming from fix-docsize.sh. This occurs in CI too. Any ideas?

Best,
Jean

fix-docsize.sh: changes.ca.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.ca.html
|
fix-docsize.sh: contribuïdor-big-page.html not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.ca.html
||
fix-docsize.sh: contribuïdor.ca.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.ca.html
||
fix-docsize.sh: essay.ca.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.ca.html
||
fix-docsize.sh: extending.ca.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.ca.html
||
fix-docsize.sh: internals.ca.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.ca.html
||
fix-docsize.sh: music-glossary.ca.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.ca.html
||
fix-docsize.sh: snippets.ca.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.ca.html
||
fix-docsize.sh: contributor.es.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.es.html
||
fix-docsize.sh: internals.es.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.es.html
||
fix-docsize.sh: music-glossary.es.pdf not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web-big-page.es.html
||
fix-docsize.sh: ../changes-big-page.ca.html not accessible from /builds/lilypond/lilypond/build/out-www/offline-root/Documentation/web/changes.ca.html
[Many more...]
|

|I opened https://gitlab.com/lilypond/lilypond/-/issues/6037 to track this.|

|Jean
|

Reply via email to