[vikunja] [error] new upgraded version doesn't start

Hello!

After upgrading vikunja from v0.24.1 to v0.24.3 the service doesn't start.

When starting the app I get the following error:

[username@schedar vikunja]$ supervisorctl start vikunja
vikunja: ERROR (spawn error)

~/logs/supervisord.log says:

2024-09-23 08:39:36,170 INFO spawned: 'vikunja' with pid 31858
2024-09-23 08:39:36,193 DEBG 'vikunja' stderr output:
supervisor: couldn't exec /home/username/vikunja/vikunja: ENOEXEC
supervisor: child process was not spawned

2024-09-23 08:39:36,194 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 140629333868840 for <Subprocess at 140629333085008 with name vikunja in state STARTING> (stdout)>
2024-09-23 08:39:36,194 DEBG fd 13 closed, stopped monitoring <POutputDispatcher at 140629333870280 for <Subprocess at 140629333085008 with name vikunja in state STARTING> (stderr)>
2024-09-23 08:39:36,194 INFO exited: vikunja (exit status 127; not expected)
2024-09-23 08:39:36,194 DEBG received SIGCLD indicating a child quit

When I start the old vikunja binary v0.24.1 manually as a test the output on the console is:

[username@schedar vikunja]$ ./vikunja
2024-09-23T10:56:12.756948201+02:00: INFO       ▶ config/InitConfig 001 Using config file: /home/username/vikunja/config.yml
⇨ http server started on [::]:3456

...and everything works fine.

But when I start the new binary v0.24.3 manually, the output is:

[username@schedar vikunja]$ ./vikunja-v0.24.3-darwin-10.15-amd64 
-bash: ./vikunja-v0.24.3-darwin-10.15-amd64: cannot execute binary file

Since this isn't my first vikunja update I'm doing (simply said, only the binary has to be changed), I'm asking if there is something with the new binary, that Uberspace can't handle? Are there any other logs I can check further?

At the moment, I switched back to the last working binary, but I would appreciate some help to get the newest update running.

Thanks!

Uberspace / lab

[vikunja] [error] new upgraded version doesn't start #1810