> Am Mittwoch, den 17. August 2022 um 13:13:44 Uhr (+0200) schrieb Orm > Finnendahl: > > Hi, > > > > after upgrading from lilpond 2.19 to 2.23, lilypond-invoke-editor and > > convert-ly stopped working. > > > > In both cases I get > > > > Traceback (most recent call last): > > File "~/bin/../libexec/convert-ly", line 24, in <module> > > import gettext > > ModuleNotFoundError: No module named 'gettext' > > > > I installed python-gettext on my systemwide python installation but it > > seems lilypond gets shipped with its own python3.10 binary and invokes > > that.
Thanks for reporting. On my system, I see an error even earlier because it cannot find the python3.10 binary. Did you move the libexec/ directory to where the wrapper script was looking for it? On Wed, 2022-08-17 at 15:11 +0200, Orm Finnendahl wrote: > Hi, > > I found the reason: In my installation the ~/bin folder was symlinked > to the bin folder of the lilypond installation and that threw it > off. The following change to the second line of the convert-ly and > lilypond-invoke-editor scripts fixes it to facilitate symlinks: > > change > > root="$(dirname $0)" > > to > > root="$(dirname "$(readlink -f "$0")")/.." > > That should be backwards compatible and work in any circumstance. Unfortunately the -f flag is not defined by POSIX, so it won't work on macOS. I'll look for a portable solution, in the meantime tracked as https://gitlab.com/lilypond/lilypond/-/issues/6406 Jonas
signature.asc
Description: This is a digitally signed message part
