Hi Mauro,
On Tue, Feb 25, 2020 at 2:21 AM Mauro Sacchetto
<mauro.sacche...@gmail.com> wrote:
>
> I'm interested in understanding if it's really a bug,
No, it is not a bug of the Debian packaging of LilyPond...
or... is it? (Please read to the very end...)
> or depends from any wrong or different setting of my system....
The error message says:
/var/lib/dpkg/tmp.ci/preinst: 1: kpsewhich: not found
which means the command kpsewhich, which is part of TeX Live, was not
found in your PATH.
Someone asked TeX Live maintainers about the same "kpsewhich: not
found" question on GitHub:
https://github.com/TeX-Live/tlcockpit/issues/10
from which you can find a helpful answer from @nobusan, i.e. fellow
Debian Developer and TeX Norbert Preining:
you have to have kpsewhich in the path, that is
you have to have /usr/local/texlive/2017/bin/ARCH in the PATH.
/usr/bin/kpsewhich is provided in the official Debian package of the
old "tetex-bin" or the new "texlive-binaries" .
But TeX Live 2019 places the kpsewhich executable file in the
/usr/local/texlive/2019/bin/x86_64-linux directory, which is in the
default PATH.
So, you might want to add it to your PATH.
Perhaps symlinking or copying
/usr/local/texlive/2019/bin/x86_64-linux/kpsewhich to
/usr/local/bin/kpsewhich would do the trick. You'll have to
experiment.
Hope this helps!
But wait... why is LilyPond preinst calling kpsewhich in the first place?
It turns out that /var/lib/dpkg/info/lilypond.preinst is a
22+-year-old script that cleans up TeX fonts stuff (my packaging
mistake), back in the time when LilyPond 1.0 relied on TeX for music
score generation... But LilyPond 2.x does not do that any more! The
lilypond.preinst script was supposed to have been dropped 11 years
ago, but was not.
Thank you so much for reporting this! You have indeed found a bug!
This ancient cruft should have been removed ages ago, and no one would
have noticed if it weren't for you! Thank you, thank you, thank you!
Cheers,
Anthony
