Broken symbolic link to spinnaker-exe.jar in py-spinnfrontendcommon package
On the EBRAINS Lab, using SpiNNaker fails because py-spinnfrontendcommon expects spinnaker-exe.jar in its build path, but the file is actually a symbolic link to a missing location in the Spack source cache.
ls -al /srv/main-spack-instance-2502/ebrains-spack-builds/vendor/spack/opt/spack/__spack_path_placeholder__/__spack_path_placeholder___/linux-ubuntu24.04-x86_64/gcc-13.3.0/py-spinnfrontendcommon-7.3.0-64eb4eiwh6fprc5ijo6oqxanymsytgyz/lib/python3.11/JavaSpiNNaker/SpiNNaker-front-end/target/spinnaker-exe.jar
lrwxrwxrwx 1 spack root 169 May 12 21:25 /srv/main-spack-instance-2502/ebrains-spack-builds/vendor/spack/opt/spack/__spack_path_placeholder__/__spack_path_placeholder___/linux-ubuntu24.04-x86_64/gcc-13.3.0/py-spinnfrontendcommon-7.3.0-64eb4eiwh6fprc5ijo6oqxanymsytgyz/lib/python3.11/JavaSpiNNaker/SpiNNaker-front-end/target/spinnaker-exe.jar -> /srv/main-spack-instance-2502/ebrains-spack-builds/vendor/spack/var/spack/cache/_source-cache/archive/8f/8fea399e835d053eb9b9b8b6f4752475d19cc3995389ca544f3ad1758007edbfThis file obviously existed during installation, but the cache seems to have been cleared at some point, leading to a broken link. This is likely a problem with the Spack package itself rather than the latest ESD release, and it should be adjusted to fetch or preserve the JAR file reliably.