On 1/18/26 2:34 AM, Hans Åberg wrote:
On 18 Jan 2026, at 07:50, Paul Scott <[email protected]> wrote:
I am posting a similar question on the Debian user list:
I install the latest development version of Lily as soon as a new one comes
out. The last step in the installation is creating a link to the binary of
lilypond I have unpacked. About 70% of the time a link command like the
following works (after removing the previous version's link).
sudo ln -s /usr/local/bin/lilypond ~/Lilypond/lilypond2.25.32/bin/lilypond
/usr/local/bin/lilypond
The repeated argument, last, should not be here.
Sorry. The repeated argument was an accident.
Currently the result is lilypond -v executing the stable version which is also
installed.
Check that the link is correctly installed with
ls -l /usr/local/bin/lilypond
and that /usr/local/bin/ is ahead in
echo $PATH
Thanks. I did all of that and the link was correct.
It turns out the problem was something I wasn't aware of that was
pointed out by a Debian user:
The solution was to execute:
hash -d lilypond
after creating the link. Or clear the entire hash with
hash -r
see: https://man7.org/linux/man-pages/man1/hash.1p.html
That indeed solved the problem.
Paul
