Re: GS version conflict in packaged 2.20 and 2.21

2020-04-19 Thread Simon Albrecht
On 19.04.20 20:27, Werner LEMBERG wrote: Do we have a warning somewhere in the LilyPond documentation that people must not use the binary directly but the wrapper? Simon, have you tried to find something in the docs? If yes, what keywords were you looking for? I have no idea from where I mig

Re: GS version conflict in packaged 2.20 and 2.21

2020-04-19 Thread Werner LEMBERG
> [...] As Jonas Hahnfeld pointed out, the problem was calling (within > the installation directory) the unwrapped binary > ./lilypond/usr/bin/lilypond (which then relied on the system default > GS) instead of the wrapper script ./bin/lilypond (which sets > environment variables such as to use t

Re: GS version conflict in packaged 2.20 and 2.21

2020-04-19 Thread Simon Albrecht
On 19.04.20 16:56, Valentin Villenave wrote: Yes, a French user also had some gs issues that I think may be related to yours: https://lists.gnu.org/archive/html/lilypond-user-fr/2020-04/msg00164.html That seems to be the same usage issue—see my parallel reply or the -user thread. Best, Simo

Re: GS version conflict in packaged 2.20 and 2.21

2020-04-19 Thread Simon Albrecht
On 18.04.20 01:46, Simon Albrecht wrote: Hello everyone, it appears from this exchange that the packaged versions of 2.20.0 and 2.21.0 contain a mixture of GS 9.21 and 9.26. Is that correct/expected/a known issue? N

Re: GS version conflict in packaged 2.20 and 2.21

2020-04-19 Thread Valentin Villenave
On 4/17/20, Simon Albrecht wrote: > it appears from this exchange > > that the packaged versions of 2.20.0 and 2.21.0 contain a mixture of GS > 9.21 and 9.26. Yes, a French user also had some gs issues that I think may be re

GS version conflict in packaged 2.20 and 2.21

2020-04-17 Thread Simon Albrecht
Hello everyone, it appears from this exchange that the packaged versions of 2.20.0 and 2.21.0 contain a mixture of GS 9.21 and 9.26. Is that correct/expected/a known issue? Best, Simon