Re: LilyPond | Pipeline #156017999 has failed for dev/hanwen/doc-build | 47b263b1 in !84

On Thu, Jun 18, 2020 at 10:18 AM Jonas Hahnfeld wrote: > > > > It would be nice to advance this MR since it seems to take about 25% > > > > off the time required for the doc stage (on my runner). > > > > > > Where do you get that 25% from, with no version of the MR passing > > > automated CI

Re: Texinfo - manual line breaks in URLs?

Am 18.06.2020 um 18:57 schrieb Werner LEMBERG: What seems most likely to me is that the indices are generated correctly, but texi2pdf refuses to generate the sorted versions. If I call texi2pdf --debug I do not see any invocations of 'texindex'. May it be that texi2pdf does not call texindex

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Donnerstag, den 18.06.2020, 19:03 +0200 schrieb Jonas Hahnfeld via Discussions on LilyPond development: > I think the way forward for now is reverting above commit, even if I > don't really like it. Unless somebody has a really clever idea how to > 1) avoid GS producing a broken PDF (if that's

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Donnerstag, den 18.06.2020, 11:21 -0600 schrieb Carl Sorensen: > On Thu, Jun 18, 2020 at 11:04 AM Jonas Hahnfeld via Discussions on > LilyPond development wrote: > > Am Donnerstag, den 18.06.2020, 00:23 +0200 schrieb Valentin Villenave: > > > On 6/17/20, Valentin Villenave wrote: > > > >

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Donnerstag, den 18.06.2020, 19:03 +0200 schrieb Jonas Hahnfeld via Discussions on LilyPond development: > Am Donnerstag, den 18.06.2020, 00:23 +0200 schrieb Valentin Villenave: > > On 6/17/20, Valentin Villenave wrote: > > > `make doc’ has been broken for nearly a week on my system (even with

Re: xdvipdfmx fails with some regtests (“Invalid object”)

On Thu, Jun 18, 2020 at 11:04 AM Jonas Hahnfeld via Discussions on LilyPond development wrote: > > Am Donnerstag, den 18.06.2020, 00:23 +0200 schrieb Valentin Villenave: > > On 6/17/20, Valentin Villenave wrote: > > > `make doc’ has been broken for nearly a week on my system (even with a > > >

Re: xdvipdfmx fails with some regtests (“Invalid object”)

Am Donnerstag, den 18.06.2020, 00:23 +0200 schrieb Valentin Villenave: > On 6/17/20, Valentin Villenave wrote: > > `make doc’ has been broken for nearly a week on my system (even with a > > clean git clone), with the following error: > > > > xdvipdfmx:fatal: typecheck: Invalid object type: -1 7

Re: Texinfo - manual line breaks in URLs?

> What seems most likely to me is that the indices are generated > correctly, but texi2pdf refuses to generate the sorted versions. > > If I call texi2pdf --debug I do not see any invocations of > 'texindex'. May it be that texi2pdf does not call texindex but use > an inlined sorting mechanism

Re: Texinfo - manual line breaks in URLs?

>> David, would you do that and fast-track this mechanical change? > > No idea what makes me the go-to here, but anyway. You replied :-) > Thanks! Werner

Re: Texinfo - manual line breaks in URLs?

>> David, would you do that and fast-track this mechanical change? > > We don't use camelcase elsewhere in Texinfo. Sounds good, thanks. Werner

Re: Texinfo - manual line breaks in URLs?

Werner LEMBERG writes: >>> Bisecting yielded that the first texinfo commit that introduced the >>> error is >>> http://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=aa18f519e091b6ada0fb2b0a65a51880031d5014 >> >> Uh oh. This looks like it introduces (modifies?) a command named >> @seealso

Re: Texinfo - manual line breaks in URLs?

Werner LEMBERG writes: >>> Bisecting yielded that the first texinfo commit that introduced the >>> error is >>> http://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=aa18f519e091b6ada0fb2b0a65a51880031d5014 >> >> Uh oh. This looks like it introduces (modifies?) a command named >> @seealso

Re: Texinfo - manual line breaks in URLs?

>> Bisecting yielded that the first texinfo commit that introduced the >> error is >> http://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=aa18f519e091b6ada0fb2b0a65a51880031d5014 > > Uh oh. This looks like it introduces (modifies?) a command named > @seealso but it would appear that we

Re: Texinfo - manual line breaks in URLs?

Am 17.06.2020 um 16:44 schrieb David Kastrup: Michael Käppler writes: Am 11.06.2020 um 15:22 schrieb Werner LEMBERG: I can prepare a version of the docs with all occurences of '@/' removed and '@urefbreakstyle before' set, so that everyone can compare and build an opinion on this. Great,

Re: LilyPond | Pipeline #156017999 has failed for dev/hanwen/doc-build | 47b263b1 in !84

On Jun 18, 2020, at 03:05, Jonas Hahnfeld wrote: > > Am Mittwoch, den 17.06.2020, 18:11 -0400 schrieb Dan Eble: >> On Jun 14, 2020, at 07:04, Han-Wen Nienhuys wrote: >>> Hey Dan, >>> >>> does your CI runner have limitations on sending data back to Gitlab by any >>> chance? It looks like this

Re: LilyPond | Pipeline #156017999 has failed for dev/hanwen/doc-build | 47b263b1 in !84

Am Donnerstag, den 18.06.2020, 10:47 +0100 schrieb James: > On 18/06/2020 09:18, Jonas Hahnfeld via Discussions on LilyPond > development wrote: > > > > Another things to consider (if you build docs locally) if to remove > > > extractpdfmark. It is extremely slow. > > Ack. > > Yes but let's not

Re: LilyPond | Pipeline #156017999 has failed for dev/hanwen/doc-build | 47b263b1 in !84

On 18/06/2020 09:18, Jonas Hahnfeld via Discussions on LilyPond development wrote: Another things to consider (if you build docs locally) if to remove extractpdfmark. It is extremely slow. Ack. Yes but let's not do that for the PDFs we eventually use for the website. The size savings are

PATCHES - Countdown for June 18th

Hello, Here is the current patch countdown list. The next countdown will be on June 20th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !166 parser: use %api.pure instead of deprecated %pure-parser -

Re: LilyPond | Pipeline #156017999 has failed for dev/hanwen/doc-build | 47b263b1 in !84

Am Donnerstag, den 18.06.2020, 09:57 +0200 schrieb Han-Wen Nienhuys: > On Thu, Jun 18, 2020 at 9:05 AM Jonas Hahnfeld wrote: > > > Would you like me to take my runner offline for a bit and trigger a > > > rebuild of this pipeline to see whether it will succeed on another runner? > > It's not

Re: LilyPond | Pipeline #156017999 has failed for dev/hanwen/doc-build | 47b263b1 in !84

On Thu, Jun 18, 2020 at 9:05 AM Jonas Hahnfeld wrote: > > Would you like me to take my runner offline for a bit and trigger a rebuild > > of this pipeline to see whether it will succeed on another runner? It's not necessary. I recreated the failing build locally. The only difference I could

Re: LilyPond | Pipeline #156017999 has failed for dev/hanwen/doc-build | 47b263b1 in !84

Am Mittwoch, den 17.06.2020, 18:11 -0400 schrieb Dan Eble: > On Jun 14, 2020, at 07:04, Han-Wen Nienhuys wrote: > > Hey Dan, > > > > does your CI runner have limitations on sending data back to Gitlab by any > > chance? It looks like this hung while uploading the failure logs > > > >