Error when clicking the menu entry "Create backup file for Lazarus":
Create backup file for Lazarus: executable "" lacks the permission to run, Errors: 1
Panic: internal error: executable "" lacks the permission to run
I have checked the permissions, even trying afterwards with the sudo lazarus-ide results with the same error.
The files involved in the original post are outdated. In the meantime lots of things have changed, including the client, the file format and so on. Lazarus also improved in the meantime. I don't think you should use those.
The client is still under development, but the activity on this subject is suspended because the latest development version of Lazarus won't compile using latest fpc stable version, as far as I know. So, there may be an incompatibility between Lazarus and Fpc versions. I expect this incompatibility to last until the release of next fpc stable version.
Regarding the error, I can only speculate that the file doesn't have permissions to be executed, permissions that may be changed by:
KDE's Dolphin: Right click on executable file, click "Properties", click "Permissions" tab, click "Advanced Permissions".
Midnight Commander: "File","Chmode"
or by typing in a terminal "chmode +x executable_file" without quotes.
The subject is not abandoned. Some plans regarding the client application:
- a console client is targeted in order to avoid unnecessary 3rd party requirements.
- the client application should be able to modify/update/install other applications: like fpc, Lazarus, fpGui, mseIDE...
- the entire update/install should be done by the client using data stored in files. Nothing specific has to be inserted inside the source code of the client.
- reduced dependencies on external applications by using multiple alternatives to update/install: for example if the user doesn't have subversion installed then the client downloads and extracts an archive, if the client doesn't have the application to extract the archive then the client downloads the data in an uncompressed format, everything automated by the client.
- possibility to insert binaries(including applications) within the file. For example having a binary file that contains both an archive and the application used to extract the archive.
- in order to achieve all these things, the client uses defines and macros all of them modifiable on the fly, internal scripting...
It's something complex, if you're interested in this alternative to update/install applications, send me a PM instead of using the now obsolete files.
All the best!