> Where can I find the source code for xdvipdfmx?
Here:
https://www.tug.org/svn/texlive/trunk/Build/source/texk/dvipdfm-x/
This is the code for a binary that gets stored under five different
names (either as links or as exact copies):
xdvipdfmx
dvipdfm
dvipdfmx
ebb
extractbb
The
> Git bisect actually tells me that xdvipdfmx started misbehaving from
> the same commit that caused gs issues:
>
> 017927b4d63c317e1fc450be2537ccc058072538 (HEAD)
> Author: Han-Wen Nienhuys
> Date: Fri Jun 5 20:36:42 2020 +0200
> Unify calling convention for command-line and API
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 (line 2161)
Git bisect actually tells me that xdvipdfmx started misbehaving from
On Jun 17, 2020, at 17:18, Han-Wen Nienhuys wrote:
>
> My proposal is to use -Werror only in CI, so we can keep code free of
> warnings.
>
I'd go along with that if I could have a single switch or environment variable
to configure my local build with all the options that will be enabled in
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
>
> -- Forwarded message -
> From: GitLab
On Mon, Jun 15, 2020 at 2:43 PM Jonas Hahnfeld wrote:
>
> Am Montag, den 15.06.2020, 07:50 -0400 schrieb Dan Eble:
> > Han-Wen proposed building with -Werror in a merge request. What do you
> > think?
> >
> > I like -Werror, but I've only ever used it where there were very few (or
> > one)
On Wed, Jun 17, 2020 at 5:26 AM Owen Lamb wrote:
>
> On Tue, Jun 16, 2020 at 12:16 AM Han-Wen Nienhuys wrote:
>>
>> On Tue, Jun 16, 2020 at 9:06 AM Werner LEMBERG wrote:
>>
>> [...] Now we have external
>> > metadata files again – not a single one, but a bunch of them...
>>
>> They're putting
On 6/16/2020 10:26 PM, Owen Lamb wrote:
I wasn't sure what to say as to my "affiliation" with LilyPond and/or GSoC
I've also had that feeling when interacting with other entities on
behalf of the LilyPond. This has happened maybe twice. In the past, I've
said something like "I am a volunteer
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, thanks in advance. I suggest that
On 6/17/20, Werner LEMBERG wrote:
> I suggest upgrading. The current maintainer of xdvipdfmx fixes bugs
> in TeXLive directly – however, this doesn't automatically update the
> binaries that are in TeXLive's SVN repository. It's not that
> complicated to get the TeXLive sources and compile a
>> It seems that you probably have to update your TeX system...
>
> Update or downgrade?
I suggest upgrading. The current maintainer of xdvipdfmx fixes bugs
in TeXLive directly – however, this doesn't automatically update the
binaries that are in TeXLive's SVN repository. It's not that
Hi,
Le 17/06/2020 à 09:53, Valentin Villenave a écrit :
Hey everybody,
`make doc’ has been broken for nearly a week on my system (even with a
clean git clone), with the following error:
No clue what your problem is, but as an aside, I can give a hint:
instead of a fresh git clone (which must
On 6/17/20, Valentin Villenave wrote:
> Thanks for giving me hope, even for a minute :-)
I spoke too soon; running doc-clean and _then_ “make doc” indeed fixes
the problem. (And Jonas has just merged it onto master so that
problem is fixed.)
Thanks!
Cheers,
-- V.
On 6/17/20, Michael Käppler wrote:
> Do you have
> https://gitlab.com/lilypond/lilypond/-/merge_requests/148/diffs?commit_id=c002d5e8c2e737cefbafa84f4b66e4b3bbc6d111
> in your repo? Otherwise that may well be the problem. Jonas wanted to
> push this one yesterday,
> but it seems that did not
Am Mittwoch, den 17.06.2020, 10:59 +0200 schrieb Michael Käppler:
> Am 17.06.2020 um 10:52 schrieb Valentin Villenave:
> > Greetings everyone,
> > I’ve noticed a recent regression with `make doc’: when it reaches
> > Documentation/ly-examples, gs fails on a bunch of files with the
> > following
Am 17.06.2020 um 10:52 schrieb Valentin Villenave:
Greetings everyone,
I’ve noticed a recent regression with `make doc’: when it reaches
Documentation/ly-examples, gs fails on a bunch of files with the
following error message:
Command: /home/work/lilypond/out/bin/lilypond -dpreview
On 6/17/20, Werner LEMBERG wrote:
> It seems that you probably have to update your TeX system...
Update or downgrade? I’m using the latest fc32 repos. Besides, I
haven’t changed anything on my OS recently and this started happening
only a week or so ago; isn’t it possible that this is triggered
Greetings everyone,
I’ve noticed a recent regression with `make doc’: when it reaches
Documentation/ly-examples, gs fails on a bunch of files with the
following error message:
Command: /home/work/lilypond/out/bin/lilypond -dpreview
-dresolution=150 -o ./out-www sesto-violin.ly
Changing working
> xdvipdfmx:fatal: typecheck: Invalid object type: -1 7 (line 2161)
>
> This is on a Fedora system with xdvipdfmx 20190225 and gs 9.52.
It seems that you probably have to update your TeX system...
https://tex.stackexchange.com/questions/490616/xdvipdfmx-typecheck-problem
If this is not a
Hey everybody,
`make doc’ has been broken for nearly a week on my system (even with a
clean git clone), with the following error:
Making input/regression/out-www/collated-files.list < 1368 files
Making input/regression/out-www/collated-files.texi < tely
Making
20 matches
Mail list logo
